Project & board templates

Templates let you standardize how teams start work across your organization. A template is a reusable blueprint — a board with its columns, a set of saved views, and the custom fields a team needs — so a new project is ready to work in one step instead of being hand-configured each time.

This page covers templates from a tenant-admin, governance angle. For the step-by-step agent workflow of instantiating and capturing templates, see Project templates.

Built-in templates

Every organization is seeded with two built-in starting points:

• Kanban — continuous flow: Backlog → To Do → In Progress → Done, with List and Board views and a Status field.
• Scrum — sprint-based: To Do → In Progress → In Review → Done, with Board and List views and Story Points plus a Status field.

Built-in templates are read-only; instantiating one never alters the template.

Standardizing with your own templates

Configure one project exactly the way you want teams to work — its board columns, its views, its custom fields — then capture it as a template. Your custom templates appear alongside the built-ins and can be rolled out to every new project, so conventions are baked in rather than re-explained.

A captured template snapshots:

• the project's board (name, kind, ordered columns),
• its saved views (name, type, configuration), and
• the relevant custom fields (key, label, kind).

NOTE

Custom fields are organization-wide. When a template is instantiated, fields that already exist are reused rather than duplicated, so your field set stays clean.

Governance tips

• Maintain a small set of blessed templates (e.g. one per delivery model) rather than letting every team invent its own structure.
• Pair templates with custom fields, saved filters, and automations so new projects arrive with the team's standards already configured.
• Revisit captured templates after process changes so new projects reflect how you work now.