Project templates

A project template is a reusable blueprint for a project: a board with its columns, a set of saved views, and the custom fields a team needs. Instead of configuring every new project by hand, you start from a template and have a ready-to-work project in one step.

Built-in templates

ActionConnect ships two built-in templates:

• Kanban — a continuous-flow board with the columns Backlog → To Do → In Progress → Done, a List and a Board view, and a Status field.
• Scrum — a sprint board with the columns To Do → In Progress → In Review → Done, a Board and a List view, and Story Points (a number field) plus a Status field.

Built-in templates are read-only starting points; instantiating one never changes the template itself.

Creating a project from a template

Pick a template and give the new project a key and a name. ActionConnect then:

1. Creates the project.
2. Creates the board and its columns (in order).
3. Adds the template's saved views to the project.
4. Defines the template's custom fields (skipping any that already exist, since custom fields are shared across the whole organization).

You can keep working in the new project immediately, or tweak the board, views, and fields afterward — instantiating copies the blueprint, it does not link back to it.

Saving a project as a template

Any configured project can be captured as your own template. ActionConnect snapshots the project's first board (its columns), the project's saved views, and your task custom fields into a new template you can reuse. Your templates appear alongside the built-in ones, marked as custom (non-built-in).

This is the fastest way to standardize how your teams start work: configure one project exactly how you like it, save it as a template, and roll it out.

What a template captures

A template's blueprint records:

• Board — name, kind (kanban or scrum), and ordered column names.
• Views — each saved view's name, type, and configuration.
• Fields — each custom field's key, label, and kind.

Optional sections are tolerated: a template with no views or no fields still instantiates a valid project and board.

Tips

• Start from Kanban for flow-based work and Scrum for sprint-based work.
• Standardize once: save a finished project as a template and reuse it.
• Pair templates with Saved filters and Automations so new projects come with the team's conventions baked in.