Templates & Task Library

Templates and the Task Library help you avoid repetitive setup work when creating implementations. Templates define a reusable set of tasks for common project types, while the Task Library provides a pool of shared tasks you can add to any implementation with a single click.

Getting There

• Click Implementations in the sidebar, then navigate to Templates (/implementations/templates) for template management
• Click Implementations in the sidebar, then navigate to Library (/implementations/library) for the shared task library
• Templates are also accessible during the create implementation wizard when choosing “Create from Template”

Implementation Templates

A template is a predefined blueprint for an implementation. It contains a name, an optional description, a category, and a list of tasks. When you create a new implementation from a template, all of the template’s tasks are copied into the new implementation as a starting point.

Why Use Templates

• Consistency — Every client gets the same baseline set of tasks for a given project type
• Speed — Skip manual task entry when starting common project types
• Standards — Encode your team’s best practices into repeatable workflows

Creating a Template

1. Navigate to Implementations then Templates
2. Click New Template
3. Enter a name for the template (e.g., “Standard Onboarding”, “Module Deployment”)
4. Add an optional description explaining when to use this template
5. Select a category to organize the template (or create a new category)
6. Add tasks to the template — each task needs at minimum a name

Tasks within a template are ordered. The order is preserved when an implementation is created from the template.

Editing a Template

1. Open the template from the Templates page
2. Edit the name, description, category, or task list
3. Changes are saved to the template

Editing a template does not affect implementations that were already created from it. Templates are copied at creation time, not linked. Existing implementations retain the tasks they had when they were created.

Template Categories

Categories help organize your templates when the list grows. Each template belongs to one category.

Categories are especially useful when your team manages many different types of client projects (e.g., “Onboarding”, “Integrations”, “Migrations”, “Custom Development”).

Deleting a Template

Admin and Lead users can delete a template from the Templates page. Deleting a template:

• Removes it from the template list
• Does not affect any implementations that were previously created from it
• Does not delete the tasks — they only existed in the template definition

Task Library

The Task Library is a shared collection of reusable tasks that can be added to any implementation. Unlike template tasks (which are tied to a specific template), library tasks are standalone and available globally.

What Is a Library Task

A library task is a task definition marked with the isLibraryTask flag. It lives in the shared library and can be inserted into any implementation. When you add a library task to an implementation, a copy is created — the library task itself remains unchanged and available for reuse.

Browsing the Library

Navigate to Implementations then Library (/implementations/library) to see all shared tasks. The library page shows:

Adding a Library Task

1. Navigate to the Library page
2. Click New Library Task
3. Enter the task name and description
4. Save the task

The task is now available for quick-add across all implementations.

Using Library Tasks in an Implementation

When editing an implementation, you can add tasks from the library:

1. Open the implementation detail page
2. Click Add Task (or the equivalent button)
3. Select From Library
4. Browse or search the available library tasks
5. Click to add one or more tasks

Each added task is a copy. You can edit it within the implementation without affecting the library version.

Editing and Deleting Library Tasks

• Edit a library task from the Library page to update its name or description. Changes apply only to the library version — implementations that already copied the task are not affected.
• Delete a library task to remove it from the library. Existing copies in implementations are not removed.

Creating an Implementation from a Template

The implementation creation wizard at /implementations/new offers a template path that combines templates with the ability to customize before finalizing.

Wizard Flow

1. Choose a path — Select “Create from Template” or “Create Blank”
2. Select a template — Browse templates organized by category and pick one
3. Review pre-populated tasks — The wizard shows all tasks from the template
4. Customize — Add, remove, or edit any of the pre-populated tasks. You can also add library tasks at this stage.
5. Select the client — Choose which client organization this implementation is for
6. Finalize — Click Create to generate the implementation with the final task list

The template serves as a starting point. Nothing prevents you from heavily modifying the task list before creating the implementation.

Template vs. Library Tasks in the Wizard

All three sources result in the same kind of task in the final implementation. Once created, there is no distinction between a task that came from a template, the library, or manual entry.

How Templates and Library Relate

Templates and the Task Library serve complementary purposes:

You can use both together. Create a template for a standard project type, then supplement individual implementations with additional library tasks as needed.

Tips & Troubleshooting

Next Steps

• Implementations Overview — Creating and managing implementations
• Implementation Views — List, Timeline, and Kanban views for working with tasks
• Roles & Permissions — Who can manage templates and library tasks
• Dashboard — Your home screen overview