> ## Documentation Index > Fetch the complete documentation index at: https://collabase.ch/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Collabase documentation. Interface labels are quoted in English, as they appear in the product. > Features marked Enterprise need the Collabase Enterprise Edition licence. # How work configuration fits together > Which work settings an administrator defines once for the instance, what a Space switches on, and what each project chooses for itself. Collabase keeps work configuration in three places. Administrators build the shared parts once: fields, work item types, workflows and project templates. A Space 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. ```mermaid theme={"dark"} flowchart TB subgraph Instance["Instance: System Settings"] F["Custom Fields"] --> C["Field Collections"] T["Work Item Types"] W["Workflows"] PT["Project Templates"] C --> PT T --> PT W --> PT end subgraph Space["Space: Space Settings"] SF["Features: Documents, Projects, Test management, Risks"] SC["Custom Fields: collections for pages"] end subgraph Project["Project: Settings tab"] PS["Status, Work Item Types, Fields, Project features"] end C --> SC PT -- "linked: managed by the template" --> PS C -- "detached or no template: chosen per project" --> PS T --> PS W --> PS ``` | Level | Where | Who | What it holds | | - | - | - | - | | **Instance** | **System Settings → Content & Organization** | System administrators | [Custom fields and field collections](/docs/admin/custom-fields), [work item types](/docs/admin/work-item-types), [workflows](/docs/admin/workflows), [project templates](/docs/projects/templates) | | **Space** | **Space Settings** | Members with the permission to manage space settings | Which apps the Space uses ([Features](/docs/concepts/space-settings#features)), which field collections apply to pages, the Permission Scheme | | **Project** | The project's **Settings** tab | Members with the permission to edit project settings | Which workflows and field collections the project uses, its own work item types, its views and features, its members ([Project settings](/docs/projects/project-settings)) | 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 project template 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. | | Linked project | Detached project | | - | - | - | | **Workflows, work item types, field collections, views** | Read-only in project settings, set by the template | Edited in project settings | | **Template changes** | Applied after each template save | Not applied | | **Name, description, members, planning settings** | Edited in project settings | Edited in project settings | How propagation works in detail: [Project templates](/docs/projects/templates#propagation).

What is fixed

Some things that other tools let you configure are fixed in Collabase. Plan around them instead of looking for a setting. | Topic | How Collabase handles it | | - | - | | **Priorities** | A fixed list: **Low**, **Medium**, **High**, **Highest**, **Blocker**. There is no screen to add, rename or reorder priorities. | | **Resolutions** | There is no separate resolution field. A work item counts as finished when its status belongs to the category **Done** or **Closed**. Add a custom field if you need to record a reason. | | **Components** | Not available. Use a **Single choice** custom field or tags to group work items within a project. | | **Tags** | Created inline on a work item or page and shared by the whole Space. There is no screen to rename or delete them. | | **Versions and releases** | Versions exist in Test Management for test coverage. Work items have no fix version field. Use [milestones](/docs/projects/approvals#phases) or a custom field to plan releases. | | **Security levels on single work items** | Not available. Restrict a whole project instead: [private projects](/docs/projects/project-settings#private-projects). |

Limits