Skip to main content
This glossary explains the terms you meet when you run and use Collabase. Each entry gives a short definition and links to the page that covers the topic in full. Terms are listed as they appear in the Collabase interface. A · B · C · D · E · F · G · H · I · K · L · M · O · P · Q · R · S · T · U · V · W

A

Accent color

The accent color is one color for the whole installation. It colors primary buttons, active navigation items and highlights for every person, in light and in dark mode. An administrator sets it under Administration → Theme. Read more about the accent color.

Action

An action is the node in an automation that does something: it creates a task, updates a page, sends a Slack message or calls an external service. Native actions work on Collabase content without any setup. Actions from external connectors need a saved Connection. Each action receives data from the nodes before it and passes its own output on.

Active Directory

Active Directory is Microsoft’s on-premises user directory. Collabase connects to it, and to other LDAP directories such as OpenLDAP and FreeIPA, so your team signs in with their existing company username and password. The LDAP settings include a preset for Active Directory that fills in the common attribute mappings. Read more about LDAP and Active Directory.

Agent

An agent is a named assistant that you define once for the whole instance, with an instruction, tools, optional knowledge and conversation starters. Members chat with it, a flow runs it in an Agent step, and jobs start it. It is not the same as an outside AI agent that you connect through MCP. Read more about agents.

Agent identity

An agent identity is a service account of its own that an agent can have. It has no password, never signs in and is never an administrator. It reads and works only in the Spaces where it was added, and it appears in the @ picker of comments in those Spaces. Read more about the identity of an agent.

Announcement

An announcement on the sign-in screen is the login announcement banner. Inside the Intranet, news comes from the published blog posts of the News Space. Read more about blog posts.

API

The Collabase REST API lets you integrate Collabase with other tools and automate work programmatically. Requests authenticate with an API key sent as a bearer token. The API is currently in closed beta and available to selected customers. Read more about the API.

App Store

The App Store adds apps to a Collabase installation. Every app ships with Collabase itself, so nothing is downloaded from outside, and a new app arrives with an update. An installed app appears for everyone in the rail under More. Read more about the App Store.

Approval node

The Approval node is a flow control node in Studio. It is not ready for production use yet and should not be used: the approver is not notified, the timeout is not applied and the automation does not continue after a decision. For approvals in projects, use gates.

Archived page

An archived page has left the page tree but keeps its content and versions. It shows the badge Archived, is listed under Archived pages in the space settings, and can be restored there. Read more about archiving pages.

Attachments macro

The Attachments macro places a live list of a page’s attached files anywhere in the page content. Readers can upload, preview and download files directly from the list, without switching to edit mode. Read more about the Attachments macro.

Attribute

An attribute is a field on an Object Type in the Registry, for example text, number, date, select, user or relation. One attribute of each Object Type is the label, the display name shown for its Objects throughout the interface. Read more about attributes.

Audit log

The audit log records changes and security events across the whole installation: sign-ins, permission changes, deletions and changes made by agents. Administrators open it under Administration → Audit Log. Read more about the audit log.

B

Backlog

The Backlog lists the open work items of a project and the cycles they are planned into. You rank the work by dragging it, then drag it into the next cycle. Read more about the Backlog.

Backup

A complete Collabase backup covers two places: the database and the file storage. There is no backup screen in Collabase; you create backups with commands on your server or through a scheduled job. Store them off the server so that a hardware failure does not take the backups with it. Read more about backups.

Base load

The base load is the share of a person’s working time taken by operations, set in percent in the workload plan. The Planner plans project work only into the rest. Read more about how capacity is calculated.

Billing rule

A billing rule tells Time Tracking how to price time entries. You define rates, multipliers, flat fees or non-billable overrides per Space, team, member or activity type, each with its own date range. Read more about billing rules.

Blog post

A blog post is a page of type Blog in a Space. The Intranet shows the published blog posts of one Space, the News Space. You cannot create a blog post in the app at the moment. Read more about blog posts.

Board

The Board shows the work items of a project as cards in columns, one column per status. You change a work item’s status by dragging its card to another column. Read more about the Board.

Burndown chart

The Cycle Burndown shows the remaining work of the active cycle against the ideal pace, with the lines Scope, Ideal and Remaining. It uses the estimates of the work items and counts work items when nothing is estimated. Read more about cycles.

C

Capacity

Capacity is the time a person or team has for planned work on a day. The Planner calculates it from the workload plan, the base load, the holidays of the holiday scheme and requested or approved absences. Read more about capacity.

Collabase Docs

Collabase Docs is the knowledge base in every Space. Pages, whiteboards and folders sit in one page tree per Space. Every save creates a version, and a private folder limits who sees the pages inside it. Read more about Collabase Docs.

Collabase Query Language (CQL)

CQL is the query syntax of the Query mode on the Search page, for example dueDate < today() AND author = currentUser(). You can save a query as a filter and run it again from My Filters. Read more about CQL and filters.

CollabaseAI

CollabaseAI is the assistant built into Collabase. It answers questions about your work items, pages, Registry Objects and test runs, and it can create and change content for you. It only sees what you can see, and every change waits for your approval. Read more about CollabaseAI.

Command palette

The command palette jumps to places; it does not search content. Press . when you are not typing in a field, then type in Search commands… to find an entry such as Home dashboard or the settings of a Space you manage. Read more about the command palette.

Condition

A condition is a node in an automation that checks a value against a rule. A Filter node stops the branch when the rule is not met; an IfElse node continues on a true or a false path.

Connection

A connection is a named, encrypted set of credentials for an external connector. You create it once in the Studio app and reuse it in every automation. Credentials never appear in execution logs.

Connector

A connector is a pre-built integration between Studio and an external service, such as Slack, Microsoft Teams, GitHub or bexio. Each connector brings its own triggers and actions.

Conversation starter

A conversation starter is a ready sentence with an icon that an agent offers in an empty chat. Choosing it sends the sentence as the first message. An agent has up to eight. Read more about conversation starters.

Cycle

A cycle is a time box, often one or two weeks, with a set of work items the team commits to. Jira calls it a sprint. A cycle is Planned, Active or Completed, and a project has one active cycle at a time. When you complete it, unfinished work moves to the backlog or a planned cycle. Read more about cycles.

D

Dependency

A dependency records that one work item has to finish before another can proceed. In Collabase it is a Blocks relation between two work items, in the same project or across projects and Spaces. Read more about dependencies.

Desktop app

The Collabase desktop app runs on macOS, Windows and Linux. It opens your own Collabase server in its own window, shows unread notifications in the menu bar or system tray, and stores nothing on the device. Read more about the desktop app.

Docker Swarm

Docker Swarm is one of the ways to run Collabase on a cluster. Collabase runs as a Swarm stack with managed secrets and rolling updates. On a single Linux server, the standard installation is the recommended path. Read more about Docker Swarm.

Documents app

The Documents app lists every attachment from pages and work items you are allowed to open, across all your Spaces. Teams use it to find a file without knowing where it was uploaded and to organize files into shared folders. Read more about the Documents app.

E

Event

An event in the Intranet is a company-wide date, such as a team meeting, an all-hands or a workshop. Upcoming events for the next 30 days appear on the Intranet home. Admins and members with the Event Manager role create them. Read more about events.

F

Field collection

A field collection is a named group of custom fields. It decides where its fields apply: on work items of the projects it is assigned to, optionally only on certain work item types, and on pages. You define each field once for the instance and reuse collections across many projects. Read more about custom fields.

File storage

File storage is where Collabase keeps uploaded files such as attachments, images and banners. The default is the server’s local disk; S3-compatible object storage is the alternative and is required for more than one application instance. Read more about file storage.

Filter

A filter is a saved search. You build it on the Search page with Filters or in Query mode with CQL, save it under a name and run it again from My Filters. Read more about filters.

Folder

A folder groups pages in the page tree under one heading. It can carry its own access list, which makes it a private folder. Create one with Create, then Folder. Read more about folders.

G

Gate

A gate ends a phase with a set of exit criteria that a person reviews before the next phase starts. A phase with a gate closes only through the gate decision, which needs the permission Decide phase gate and is kept with its rationale. Read more about gates.

Global module

A global module is an app that is not tied to a Space: Registry, Studio, Intranet and Times. Access to a global module is granted to groups per module under Admin → Roles & App Access. Read more about permissions.

Governed workflow

A governed workflow allows only the status transitions you have configured explicitly. Any other move is blocked. Use it for regulated or audit-sensitive processes. Read more about workflows.

Grace period

The grace period is the 14 days after a licence key reaches its end date. Enterprise features stay on, and the header counts down the days left. After it ends, the licence is expired and the interface is read-only. Read more about the grace period.

Group

A group is a set of members managed under Admin → Groups. An administrator grants a group access to a Space on the group’s Space Access tab, and all its members get the space role assigned there. A group can also hold roles for global apps. Read more about users and groups.

H

Holiday scheme

A holiday scheme is a named list of non-working days for a country, region and calendar year. Workload plans use it so that holidays show no daily hour target in the time calendar. Read more about holiday schemes.

I

Identity provider

An identity provider is the system your team already uses to sign in, such as Microsoft Entra ID, Okta, Keycloak or Google. Collabase connects to identity providers through OAuth, SAML, LDAP and SCIM, under Admin → Identity Providers. Email and password sign-in stays available as a fallback. Read more about identity providers.

Initiative

An initiative is a theme or goal on a roadmap that you plan with a period, a status and an owner. It can link projects, work items, portfolios and pages. A project has no initiatives: an initiative sits one level above and points at projects. Read more about roadmaps.

Inline comment

An inline comment is attached to text you select on a page. The text is highlighted, and the comment appears next to its block. Read more about comments.

Instance role

Every account has an instance role: Admin has full access to all settings and all Spaces, User works in the Spaces they are invited to. Instance roles are set under Admin → Users. Read more about instance roles.

Intranet

The Intranet is the internal communication hub of Collabase. It brings news, events, quick links and birthdays together for everyone in the organization. Read more about the Intranet.

K

Kubernetes

Collabase runs in an existing Kubernetes cluster with the official Helm chart. If you have a single Linux server, you do not need Kubernetes; the standard installation is simpler and fully supported. Read more about Kubernetes.

L

Licence key

A licence key decides which edition of Collabase is active. With a valid Enterprise key, the Enterprise features switch on without a new installation or a restart. Administrators enter it on the License & System page. Read more about licence keys.

Linked and detached projects

A project created from a project template is linked to it: its features, statuses, work item types and fields are read-only and follow changes to the template. Detaching the project gives it its own copies of the configuration and stops template changes from reaching it. Detaching cannot be undone. Read more about linked projects.

Live collaboration

Live collaboration lets several people edit the same page at once. Everyone sees the others’ changes as they type, along with their cursors and presence avatars. It is on by default and an administrator can turn it off. Read more about live collaboration.

Login announcement banner

The login announcement banner shows a notice above the sign-in form, for example planned maintenance. People see it before they sign in. An administrator sets its title, text and color under Administration → Login screen. Read more about the announcement banner.

M

Macro

A macro shows live content from Collabase inside a page, such as Collabase Tasks, a table of work items, or Attachments, a list of the page’s files. Macros update when the data changes. Read more about macros.

Mail event

A mail event is one kind of mail Collabase can send, such as task-assigned. Administration → Mail Templates lists every event for review. Which kinds of mail members get is set per category under Administration → Notifications. Read more about notification defaults.

MCP

MCP (Model Context Protocol) is an open standard for connecting AI applications to other systems. Collabase uses it in two directions: clients such as Claude or Cursor connect to Collabase, and Collabase connects to MCP servers of other systems. Read more about the Collabase MCP server.

MCP server

An MCP server offers tools, for example a search in a documentation set. An administrator connects it once under Admin → Settings → AI settings → MCP servers, and its tools are then available in every CollabaseAI and agent chat. A tool that changes something asks for approval first. Read more about MCP servers.

Member

A member is a person with a Collabase account. Inside a Space, each member has a space role that decides what they can do there. Read more about Space members.

O

Object

An Object is a single record in the Registry, for example one server, one vendor or one contract. Its fields are the attributes of its Object Type, and it can be linked to other Objects and to tasks. Read more about the Object Browser.

Object Type

An Object Type defines a category of record in a Registry schema, such as Customer, Server or Contract. It has a name, an icon, a color and a set of attributes. Read more about Object Types.

P

Page

A page is the core unit of Collabase Docs. The page tree of a Space holds three kinds of items: pages for rich text, whiteboards for drawing, and folders that group pages. Every save of a page creates a version. Read more about pages.

Page status

The page status tells readers how far the content is: Draft, In Progress, In Review, Published or Verified. New pages and copies start in Draft, and project guests never see draft pages. Read more about page status.

PDF template

A PDF template sets the look of a page exported to PDF: colors, cover page, table of contents, numbered headings and a watermark. Administrators manage templates under Administration → PDF Templates. Read more about PDF templates.

Permission Scheme

A Permission Scheme is a reusable template that defines what Managers, Members and Viewers can do in a Space. One scheme can be assigned to many Spaces, and a change to it updates all of them at once. Collabase ships with four built-in schemes that you can clone and adapt. Read more about Permission Schemes.

Phase

A phase is a stage a project runs through, such as initiation, concept or realisation, with a start and an end. A phase closes with Complete phase or, when it has a gate, with the gate decision. Phases show as bands on the timeline. Read more about phases.

Planner

The Planner shows, for the next four weeks, how much time each person or team has and how much work is planned for them, across every project. It needs the app right Times and opens under Times → Planner. Read more about the Planner.

Portfolio

A portfolio collects projects from any Space under one owner and one budget. The Portfolios page shows them in a table with the traffic light of each project’s status report, and on one Gantt chart. Read more about portfolios.

Private folder

A private folder has its own access list: only the people and groups on it see the folder and every page below it. Its author, the Space owner and instance administrators always see it. Private folders and restricted pages are the restricted zones of a Space. Read more about private folders.

Profile

Your profile holds your name, job title, language, notification settings, password and API tokens. All profile settings affect only your own account. Read more about your profile.

Programme

A programme is simply a portfolio that sits under another portfolio, with the same screen and the same features. Portfolios nest without a depth limit. Read more about how portfolios are structured.

Project

A project is where a team tracks its work inside a Space: work items that move through the statuses of a workflow, with views such as Board, Work Items, Timeline and Backlog, and optional features such as cycles, phases and gates, risks and costs. Read more about Projects.

Project template

A project template is the starting configuration for new projects. It bundles workflows, work item types, field collections, the views a project shows, the fields a project must fill in and an optional phase model. Templates are available in every Space, and projects created from one stay linked to it. Read more about project templates.

Q

Quick links are pinned shortcuts on the Intranet home. Organization links are set by admins and visible to everyone; personal links are visible only to the member who added them. Read more about quick links.

R

Registry

The Registry is the structured data store of Collabase. You define your own Object Types, create Objects and link them with typed relations, for customers, assets, vendors, contracts or anything else you track. It is an instance-wide module, not tied to a Space. Read more about the Registry.

Relation

A relation is a directed, typed link between two Objects in the Registry, for example “Server runs Application”. You draw relations between Object Types in the Schema Designer and view connected Objects as a graph or a list. Read more about the Schema Designer.

Relation graph

The Relation Graph shows a work item with its relations, sub-items, linked pages and test cases, up to four steps deep and across projects. Open it with Graph in the top bar of a work item. Read more about the relation graph.

Restricted zone

A restricted zone is a folder or page with its own access restrictions. Zones in the space settings lists every restricted zone of a Space. Read more about restricted zones.

Risk register

The risk register lists what could go wrong in the projects of a Space, rated by probability and impact on a 3 by 3 matrix. Risks are Registry Objects, and each can name an owner, a project and the work item that handles it. Read more about the risk register.

S

Roadmap

A roadmap plans initiatives over time across projects, portfolios, work items and pages. Dates are set by hand and nothing is calculated. It does not replace the Timeline of a project. Read more about roadmaps.

SAML

SAML 2.0 is a standard for single sign-on. Collabase works with Okta, Microsoft Entra ID and any other SAML 2.0-compatible identity provider. Read more about SAML SSO.

Schema

A schema is the top-level container of a data model in the Registry. It groups Object Types, their attributes and the relations between them, for example one schema for IT assets and another for vendor management. Read more about schemas.

Schema Designer

The Schema Designer is the visual canvas for building a Registry data model. Object Types appear as nodes and relations as arrows, and you edit the model by clicking on the canvas. Read more about the Schema Designer.

SCIM

SCIM 2.0 is a standard for automated user provisioning. Connected to your identity provider, it creates, updates and deactivates Collabase accounts and group memberships automatically. Read more about SCIM. Collabase has one search across all content you have access to: tasks, pages, Registry Objects, test cases, test runs and automations. Open it with Cmd + K on Mac or Ctrl + K on Windows and Linux. Read more about search.

Search index

The search index holds the searchable text of pages and is kept in the database. Administrators see its state and rebuild it under Administration → Search Index. Read more about the search index.

Seat

A seat is an internal person who can sign in: an active account with the role Admin or User. Guests, locked and anonymized accounts do not take a seat. When every seat is taken, Collabase refuses new accounts and reactivations. Read more about seats.

Security policies

Security policies control how long a sign-in stays valid, lock out repeated failed logins and let named people sign in with a password when SSO is enforced. You find them under Settings → Security → Policies. Read more about security policies. Semantic search finds content by meaning instead of exact words. When an administrator enables it in the AI settings, CollabaseAI uses it to find the relevant pages, work item descriptions and comments and answers with links to them. The header search and the Search page match words, not meaning. Read more about search.

Skill center

The skill center is the dialog on the Tools card of an agent, opened with Add skills. It lists the skills of CollabaseAI by app, the actions of installed plugs and the tools of MCP servers, and adds or removes them for the agent. Read more about the skill center.

Space

A Space is the top-level container in Collabase, with its own members, apps and content. Think of it as a department, a product area or a team. Spaces are isolated from each other, which makes them a reliable boundary for access control. Read more about Spaces.

Space role

Inside a Space, every member has one of four roles: Space Admin, Manager, Member or Viewer. The Space Admin role has fixed rights; the other three are defined by the Space’s Permission Scheme. Read more about Space roles.

Space settings

Space settings configure one Space: its name and owner, translation, features, members, roles and Permission Scheme, visibility, restricted zones, page structure, custom fields, archived pages and deletion. They open only for people with the right to manage the Space’s settings. Read more about Space settings.

Sprint

Sprint is the Jira term for what Collabase calls a cycle. Read more about cycles.

Status category

Every workflow status belongs to one of four categories: To Do, In Progress, Done or Closed. The category tells Collabase how to treat work items in that status, whatever the status is called. Done and Closed give the work item a completion date; Closed is for work finished without being done, such as a rejected request. Read more about status categories.

Status report

A status report is the monthly report a project manager writes on a project’s Reports tab. It carries a traffic light, text sections and figures, is reviewed, and is frozen once approved. Read more about status reports.

Story points

Story points are a relative effort estimate on a work item, in the Fibonacci sequence from 0 to 21. Collabase uses them for the burndown and velocity of cycles. A project can estimate in T-shirt sizes or hours instead. Read more about estimation.

Studio

Studio, called Collabase Automation before, is the workflow app built into Collabase. You connect a trigger, conditions and actions in a visual drag-and-drop builder, without writing code. Every run is logged with the input, output and status of each node.

Suggestion

A suggestion is a proposed change to a page’s text, made by a reader without editing the page. The author or an editor reviews it and accepts or rejects it. Read more about suggestions.

Swimlane

A swimlane divides the columns of a board into horizontal rows, one row per value of a chosen field such as assignee or priority. Read more about swimlanes.

System ID

The System ID identifies one Collabase installation, in the form CBASE-XXXX-XXXX-XXXX. You send it with a licence request. It is stored in the database, so it stays the same across updates and restores. Read more about the License & System page.

System Settings

System Settings hold every setting that applies to the whole installation, from branding and mail to the search index. They open from the profile menu for accounts with the Admin instance role. Settings of one Space are in its space settings. Read more about System Settings.

T

Task

A task is a single unit of work in a project, such as a feature request, a bug or a support ticket. Collabase shows it on screen as a work item. It has a permanent key like PROJ-42, a status, a type, a priority and an assignee. Read more about tasks.

Template

A template in Collabase Docs is a reusable page structure. It can contain placeholder variables in {{variable}} format that are prompted when someone creates a page from it. Read more about templates.

Test case

A test case describes one thing to verify, with ordered steps and the expected result for each. Every change is a new version, and only an approved version can be run. Read more about test cases.

Test cycle

A test cycle is one round of testing, for example the regression test before a release. It holds one execution per planned case, and every result recorded for an execution is kept. Read more about test cycles.

Test folder

A test folder groups test cases inside a test project. Folders nest to any depth and have no effect on execution. Read more about test cases.

Test Management

Test Management is the quality app in every Space. You keep versioned test cases, run them in cycles, import CI results and see which requirements are covered. Read more about Test Management.

Time account

A time account is a named billing container that groups time entries by client, retainer or cost center, so reports show what was logged against each. Read more about time accounts.

Time Tracking

Time Tracking lets your team log hours against tasks and projects, submit monthly timesheets for approval and produce billable reports. Read more about Time Tracking.

Timeline

The Timeline tab of a project shows each work item with dates as a bar on a calendar. You drag bars to reschedule, draw arrows for what blocks what, and see cycles, phases and milestones in the same picture. It plans one project and can calculate the critical path; a roadmap is the overview across projects. Read more about the Timeline.

Timesheet

A timesheet is a monthly period of time entries. It moves from DRAFT to SUBMITTED to APPROVED; once approved, its entries are permanently locked. Read more about timesheets.

Traffic light

The traffic light rates a project as On track, At risk or Critical in its status report. The traffic light of the newest approved report appears on the Portfolios page. Read more about status reports.

Transition

A transition connects two statuses of a workflow. Only the transitions drawn in the workflow are offered on a work item, as buttons labelled with the transition name. A transition can carry conditions, validators and functions. Read more about transitions.

Trash

The trash holds deleted Spaces, projects, pages and work items. Projects and work items are deleted for good after 30 days; Spaces and pages stay until an administrator restores them or deletes them for good. Read more about the trash.

Trigger

A trigger starts an automation. It can be a Collabase event, a schedule, a webhook, a manual run or an event from a connected service. Every automation has exactly one trigger.

U

Update

An update brings your installation to a new Collabase version with one command, bash update.sh. The script backs up the database first, downloads the new version and restarts the services. Read more about updates.

V

Validator

A validator is a rule on a workflow transition that blocks the move and tells the member why, for example when a required field is empty or sub-items are still open. Read more about rules on a transition.

Version

A version is a saved state of a page. Collabase creates one with every save of the page content, including automatic saves while you type. It records its number, author and time, and the title, icon and status the page had. Read more about versions.

Version history

The version history of a page lists every version, newest first. You can look at a version, compare two versions and restore one. It opens from Page info on the Versions tab. Read more about version history.

Visibility

A Space’s visibility decides who can read it without being a member. By default only members can. With Make space public switched on, every signed-in user can read its pages. Read more about Space visibility.

W

Whiteboard

A whiteboard is a drawing board in Collabase Docs for diagrams, wireframes and sketches, with shape libraries. It sits in the page tree like a page and saves about 5 seconds after you stop drawing. Read more about whiteboards.

Work item

Work item is the name Collabase uses on screen for a task in a project. Both terms mean the same thing. Read more about tasks.

Work item type

A work item type names a kind of work, such as Bug, Feature or Change Request. The type decides which field collections and which workflow apply to a work item. Administrators manage types under System Settings → Content & Organization → Work Item Types. Read more about work item types.

Work Items table

The Work Items tab shows the work items of a project as a table. Use it to scan, sort or correct many items at once. Read more about the Work Items table.

Workflow

A workflow is the set of statuses a work item moves through and the transitions between them. Workflows are designed once for the instance; projects and project templates pick the ones they use. Read more about workflows.

Workload plan

A workload plan sets a person’s or a team’s working time: hours per day, work days and a Base load (%). The Planner uses it to calculate capacity. Without any plan, Collabase assumes 8 hours a day, Monday to Friday. Read more about how capacity is calculated.

Worklog attribute

A worklog attribute is a custom field on every time entry, for example activity type, service category or a travel flag. Read more about worklog attributes.

Writing assistant

The writing assistant generates, summarizes, translates and improves text in any editor in Collabase. Type /ai on any line to open it. Read more about the writing assistant.
Last modified on November 4, 2026