# Project templates

A company's mould for its projects: roles, policies, folders and notes copied into each new one.

Source: https://ardumaker.com/en/docs/plantillas/

- Category: Projects and companies
- Status: Available
- Requirements: Be a company admin to create or edit templates; To apply it: the company must be associated with the project
- MCP tools (Write or modify): `crear_proyecto`, `crear_proyecto_con_etapas`

## What can you do with it?

A template is the mould a company's projects start from. It can contain:

- Roles with their per-section permissions already trimmed.
- Policies (PDF or text) that must be signed to join.
- Folders and base notes, links or files.

A company can have several templates and mark one as the default.

## When should you use it?

- When the company builds similar projects and always repeats the same roles and policies.
- So you do not forget to close a section for a role, such as the client role.

## How does it work in ArduMaker?

1. A new template starts with the same 14 roles as a new project, with full permissions, to trim rather than write from scratch.
2. When a project is created, the chosen template is applied or, if none is chosen, the default of each associated company. A project can also be created without a template.
3. When a company is added to an existing project, its default template is applied without overwriting the roles the project already has.

> **INFO:** What gets applied is a **copy**: once applied, the project keeps no link to the template. Changing it does not affect projects that already started.

- It is applied in a transaction: all of it or nothing.
- It is idempotent by name: applying it twice fills in what is missing without duplicating.
- Files (policy PDFs, attachments) are copied, not shared.

## What actually changes?

- In the project: roles, policies with their version 1, folders and new attachments.
- A line in the history with the applied template's name.
- Deleting a template deactivates it; it is not removed.

## Diagram

**Applying a template**

```text
Company template (roles, policies, folders, notes)
  ↓
Copy in a transaction (idempotent by name)
  ↓
Project (with its own copies, no link)
  ↓
History (applied template name)
```

## Expected result

The project starts with the template's roles, [policies](https://ardumaker.com/en/docs/firma-de-documentos) and material, and the creation response states how many items of each kind it left.

## Errors and troubleshooting

| Message | Cause |
| --- | --- |
| `Only an admin of this company can manage its project templates` | The editor is not a company admin. |
| `Template not found` | It does not exist or is deactivated. |
| `That template belongs to a company that is not part of this project` | The template belongs to a company not associated with the project. |

If applying the template fails, the project is still created, without the template.

## MCP access

An MCP agent does not create or edit templates. It does use them when creating projects:

- `crear_proyecto` accepts `plantilla_id`: `por_defecto` (like the web form), an id, or `null` to apply none.
- `crear_proyecto_con_etapas` always applies the default template.

More at [/mcp/proyectos](https://ardumaker.com/en/mcp/proyectos) and [/mcp/docs](https://ardumaker.com/en/mcp/docs).

## Related features

- [Companies](https://ardumaker.com/en/docs/empresas/)
- [Roles and permissions](https://ardumaker.com/en/docs/roles-y-permisos/)
- [Document signing](https://ardumaker.com/en/docs/firma-de-documentos/)
- [Attachments](https://ardumaker.com/en/docs/archivos-adjuntos/)
- [Projects and kanban board](https://ardumaker.com/en/docs/proyectos-kanban/)