Skip to main content
Collabase keeps work configuration in three places. Administrators build the shared parts once: fields, work item types, workflows and project templates. A decides which apps it uses. Each project then picks from the shared parts, either by itself or through a linked template. There is no split into two kinds of projects. Every project uses the same building blocks; what differs is whether a template keeps them in step.

The three levels

The diagram shows where each building block is defined and who uses it. Arrows point from the place where something is defined to the place where it is used. Open System Settings from your avatar menu or from Settings at the bottom of the app sidebar. The entry appears only for system administrators.

Linked and detached projects

A project created from a stays linked to it. While it is linked, the template decides the project’s workflows, work item types, field collections and views, and the project settings show those sections read-only. When an administrator saves the template, linked projects receive the change in the background. Detach a project when its team needs to change these settings itself. Detaching cannot be undone. The project keeps its current configuration and stops receiving template changes. How propagation works in detail: Project templates.

What is fixed

Some things that other tools let you configure are fixed in Collabase. Plan around them instead of looking for a setting.

Limits

These limits are fixed. An administrator cannot change them in the interface. There is no fixed limit on the number of custom fields, field collections, choices, statuses, transitions or work item types.

Custom fields

Build the field library and group fields into collections.

Workflows

Design statuses, transitions and the rules on them.

Project templates

Bundle the configuration for new projects.

Set up projects for a team

The order in which to build it all.
Last modified on October 13, 2026