Help Center / Templates and template library /
Templates overview
Instead of rebuilding the same project structure, invoice layout, or proposal design from scratch each time, templates capture the full configuration of an entity and make it reusable. Templates exist across nearly every area: projects, tasks, task boards, invoices, proposals, contracts, forms, wikis, custom pages, automations, and booking pages. Saving an entity as a template preserves its blocks, fields, layout, and settings, so the next time that same structure is needed, the setup is already done.
What a template captures
A template isn't just a name and a few defaults. Saving a project as a template preserves its task boards, task structure, statuses, and assignee roles. Saving a proposal preserves the block layout, service table pricing, text content, and signature block placement. Saving an automation preserves the trigger, conditions, actions, and field mappings. Each type's template captures everything that makes the entity work, not just its title.
Where templates connect
Templates feed into the creation flow of every supported entity. When a new project, invoice, proposal, form, or any other supported entity gets created, a template can be selected as the starting point. The template pre-fills the new entity with the saved structure and content, and everything remains fully editable after applying. Templates are a starting point, not a locked format.
The template library
Beyond templates saved from your own entities, a community template library offers pre-built templates shared by other Plutio workspaces. Templates can be browsed by type and category, previewed before installing, and customised after installation. Because templates span projects, tasks, invoices, proposals, contracts, forms, wikis, custom pages, automations, and booking pages, the same reusable pattern works consistently across your entire workspace.
