.png?fit=max&auto=format&n=V5LGcGniNC1X_QJO&q=85&s=8c9ba3ce9a0d0045976180c9f669af26){kind=logo}
Project Templates
A project template is a saved configuration that bundles a workflow, task types, field collections, and the set of views (board, backlog, sprints, etc.) enabled for a project. When a team creates a new project and selects a template, the full configuration is applied automatically — no manual setup needed. Templates are managed by administrators under Admin → Project Templates.Template components
Template scope
Creating a template
1
Open Project Templates
Go to Admin → Project Templates and click + New Template.
2
Set the name, icon, and description
Give the template a clear name that describes the use case (e.g. “IT Service Desk”, “Software Sprint”, “Customer Onboarding”). Add an optional description so project creators know what the template is for.
3
Assign a workflow
Select one or more workflows from the list of global workflows. Mark one as the default — this is the workflow applied when a project is created from the template.
Only workflows created under Admin → Workflows appear here. Create your workflow there first if it does not appear in the list.
4
Assign task types
Select the task types to include. Mark one as the default type — new tasks will use this type unless the user changes it. Task types must exist at the global level (Admin → Task Types) before they can be added to a template.
5
Assign field collections
Select one or more field collections to attach. All custom fields in those collections will be available on tasks in projects created from this template.
6
Choose enabled views
Toggle which project views are enabled. Disabling a view removes it from the navigation for all projects created from this template.
7
Publish the template
Enable the Published toggle to make the template available in the project creation gallery. Unpublished templates are only visible to administrators.
8
Save
Click Save. The template is now available when creating a project.
Editing a template
Open a template from the gallery and click Edit. You can change the name, description, workflow, task types, field collections, or enabled views at any time.Propagating changes to linked projects
Every time you save structural changes to a template (adding/removing a workflow, task type, or field collection), the template’s version number increments. Collabase detects which linked projects are behind the current version. To push the updated configuration to all linked projects, click Propagate to linked projects on the template detail page. This applies the changes to every project that is still linked to this template and has not been detached.Deleting a template
Click Delete on a template to remove it. Deleting a template does not delete the projects that were created from it — it only breaks the template link. Affected projects are automatically detached and keep their current configuration.Linked vs. detached projects
A project created from a template stays linked to it by default. Linked projects can receive propagated updates from the template. A project can be detached from its template at any time from Project → Settings → General → Detach from template. After detaching:- The project keeps its current workflow, task types, and field collections.
- It no longer appears in the list of linked projects for the template.
- Future template changes do not affect it.
Setup checklist
Before creating a template, make sure these exist at the global level:- At least one workflow configured in Admin → Workflows
- Task types configured in Admin → Task Types (if you want per-type field rules)
- Field collections configured in Admin → Custom Fields → Collections (if you need custom fields)