In short.
Collabase AI is the assistant of the Swiss platform Collabase. It reads work items, pages and comments with the permissions of the person asking, and changes nothing without approval. You bring your own provider and key, and it stays off until an administrator releases it.
Off until you switch it on
AI is disabled by default. An administrator enables it for the instance
The provider you choose
OpenAI, Anthropic, Gemini, or Infomaniak when processing has to stay in Switzerland
Nothing without approval
Every change arrives as a card with approve and reject, and it cannot be switched off
Only what you may see
The assistant works with the permissions of the person asking, space by space and page by page
When the answer is in the house and nobody finds it anyway.
The reasoning behind a decision sits in a comment under a work item that closed a year ago. The status report for management is written by hand every Friday. And external AI is out of the question, because the content may not leave the building. Collabase AI addresses exactly those three points.
The knowledge sits in comments and histories that a keyword search never reaches.
Reports on progress, delay and blockers are written by hand instead of read from the data.
External AI services are ruled out, while a model on your own server would be allowed.
What you get out of it.
An assistant that reads your own material
The chat panel opens with Cmd + J and knows what is on screen. It finds work items and reads pages, cycles, comments, Registry objects and test runs, then answers from them. When it finds nothing it says so and names what it looked for, instead of inventing an answer.
Approval before every change
A new work item, a changed status, a comment: every write comes back as a card naming exactly what would happen. Nothing occurs without a yes. This is not a politeness setting but the protection against a sentence inside someone else's page being read as an instruction. That is why it cannot be switched off.
Writing where the writing happens
Typing /ai on any line opens the actions: generate text, summarize, shorten, expand, fix spelling, continue writing, translate. In Docs pages, in work item descriptions, in Intranet posts and in Registry text fields.
Search by meaning, with sources
A question in your own words finds the right passage even when it uses different wording. Pages, work item descriptions and comments are searched, and the sources are listed as links at the end of the answer. The comments are the part that surprises people: that is usually where the reasoning sits, not in the page itself.
You decide where the computing happens
The operator picks the provider once and every feature uses it. With Infomaniak the processing stays in Switzerland. OpenAI, Anthropic and Gemini bring larger models and their own terms. Language model, embedding and re-ranking can be filled separately, each with its own provider and its own key.
The key is yours, and with it the decision.
Collabase AI is opt-in and off on delivery. Whoever switches it on brings their own access to the language model: your contract with the provider, your API key, your billing. That also puts the choice of model, the processing region and the compliance that comes with it in your hands. Collabase makes the connection and processes nothing on its own account.
Who this pays off for.
Project management
What is overdue, what is blocked, and how the last cycle stood against what it committed to.
Knowledge management
Answers from your own pages and comments, with a link to where they came from.
Quality assurance
What failed in the last test run, together with the tester's comment.
IT operations
Read and change Registry objects, with permissions checked per object rather than per space.
Collabase AI sits across all seven apps.
The assistant is not an eighth app beside the others but the layer above them. It reads Projects, Docs, Registry and Test Management through the same sign-in and the same permissions, the writing assistant works in every editor, and the AI blocks in Automation use the same provider. One contract, one operation, one point of contact.
Docs
Projects
Intranet
Registry
Test Management
Automation
Time
Operations and data sovereignty.
Where the data sits is decided by the operating model, not by the small print.
Swiss hosted
Operated on Swiss public cloud at Infomaniak, one isolated environment per customer. Content is processed in Switzerland only, apart from the upstream web application firewall.
Self-hosted
Runs on your own infrastructure. Full control over the data, no access from outside.
revFADP & GDPR
Data processing agreement included. Compliant with the revised Swiss data protection act and the GDPR.
One product, all apps.
Collabase Enterprise
On request
Staged by user count
Collabase AI is part of the Enterprise plan. All seven apps, no add-ons.
Questions from first conversations.
Collabase AI in practice: what comes up most often in a first conversation.
Is the AI switched on by default?
No. It is disabled until an administrator releases it for the instance, and it is then enabled per space. Without that release, no content leaves the environment.
Which provider processes our content?
The one you connect yourself, with your own key: OpenAI, Anthropic, Gemini, or Infomaniak when processing has to stay in Switzerland. Collabase does not run a model of its own in between.
Can the assistant change content without asking?
No. Every change appears as a proposal with approve and reject. That confirmation step cannot be switched off.
Does the assistant see more than the person asking?
No. It works with the permissions of the person asking, space by space and page by page. What someone is not allowed to open does not appear in an answer either.
Try Collabase AI on your own material.
In the proof of concept we set up the provider of your choice, index part of your content, and you ask the questions that stay open in everyday work.