# Document signing

Project policies and documents signed with name and signature, with immutable versions and a verifiable PDF.

Source: https://ardumaker.com/en/docs/firma-de-documentos/

- Category: Projects and companies
- Status: Available
- Requirements: An ArduMaker account; To publish a project's policies: be its manager
- MCP tools: No MCP tools: it is used from the dashboard.

## What can you do with it?

- Let a project manager publish **policies** (PDF or text) that must be signed to join, per role or for everyone.
- Sign by typing your full name and, on documents, with a saved signature.
- See what is pending and download the PDF of what was signed.
- Validate any signed PDF, without an account, to learn whether it is intact and who signed what.

| Scope | Who requests it |
| --- | --- |
| `plataforma` | ArduMaker to its users (terms, privacy) |
| `empresa` | A company to its members |
| `proyecto` | A project to its members |

## When should you use it?

- So nobody joins a client project without accepting its rules.
- To have a signed paper a third party can verify.

## How does it work in ArduMaker?

### Project policies

- A version is immutable and carries its `sha256`. Changing the policy publishes a new version.
- A new version requires re-signing unless the manager marks it as a minor change.
- By default it only applies to people who join after it is created; it can be extended to current members. It never applies to the manager.
- Whoever has not signed cannot enter the project, but can always read the policy, sign it or leave the project.
- If the policy is a PDF, ArduMaker tries to prepare it for signing with the signing tool; if it cannot, it is published anyway and the signature is recorded without a PDF.

### Signed documents

- Signing produces a PDF with the signature, date, user and an internal history that allows verifying it later.
- `individual` mode: each person signs their own copy. `conjunto` mode: a single file with several signers.
- Each document decides whether it **blocks** or only **warns**; by default it warns.
- Platform and company documents are published by ArduMaker from its administration.

## What actually changes?

- Signing stores the signature (with IP and browser) tied to the exact signed version.
- A signature is never deleted: not when the policy is deactivated, the role changes or the person leaves the project.
- Deleting a policy deactivates it; its signatures stay stored.
- Validating a PDF does not store it.

## Diagram

**Joining a project with a policy**

```text
New member (with an affected role)
  ↓
Pending policy (read, sign or leave)
  ↓
Signature (typed name + exact version)
  ↓
Project open (according to role)
```

## Expected result

The person joins the project and the signature appears in the policy's signature book, visible only to the manager. If there was a PDF, it is available for download from the signed list.

## Errors and troubleshooting

- An error with type `politica_pendiente` means a policy must be signed before continuing.
- On documents, signing the same version twice is rejected; on a project policy, repeating the signature returns the existing one.
- Public validation accepts files up to 20 MB and 10 requests per minute per IP.
- Validating an altered PDF is not an error: the response says it is not intact and lists the problems.

> **PRECAUCION:** A role-scoped policy needs at least one role selected; applying it to current members immediately blocks those who have not signed.

## MCP access

There is no MCP access. No agent can create, edit or delete a policy, or sign one: signing is a personal act.

Full reference for each tool: [/mcp/docs](https://ardumaker.com/en/mcp/docs).

## Related features

- [Roles and permissions](https://ardumaker.com/en/docs/roles-y-permisos/)
- [Project templates](https://ardumaker.com/en/docs/plantillas/)
- [Companies](https://ardumaker.com/en/docs/empresas/)
- [Projects and kanban board](https://ardumaker.com/en/docs/proyectos-kanban/)