Collabase ai

CollabaseAI is the assistant that sits inside Collabase itself. It answers questions about the work you already have in the platform, and it can act on that work: creating pages and whiteboards, opening and changing work items, writing comments. It only ever sees what you can see. Every question it answers is scoped to your own permissions, so a space, project or page you cannot open is a space, project or page it cannot read for you either.

---

​

Opening the assistant

The launcher sits at the bottom centre of every screen, in the middle of the small dock next to search and create. Click it to open the chat panel. If the launcher is not there, an administrator has not enabled AI on this instance yet. See AI Configuration.

---

​

Using the panel

The panel floats above the page, so whatever you were reading stays in view behind it.

​

Resizing

Drag the top edge of the panel to make it taller, and the right edge to make it wider. The size is remembered on your device and applies the next time you open it.

​

Suggestion chips

Above the input field is a row of starting points. What they offer depends on what you have open.

​

The context pill

When you open the panel while a work item, page or Registry object is on screen, a small pill under the header names it. That is what CollabaseAI is reading, so you can ask “what changed here?” without naming the item.

---

​

What you can ask for

CollabaseAI works in two directions: it looks things up, and it changes things. Every skill it has, with an example of how to ask for it, is listed in the skill reference.

​

Before it changes anything

CollabaseAI never writes on its own. Creating a work item or a page, changing a field, moving an item, posting a comment: each one arrives in the chat as a card naming exactly what it would do, with Approve and Reject. Nothing happens until you approve, and rejecting changes nothing. This cannot be switched off. CollabaseAI reads pages, work items and comments written by other people, and a sentence inside one of them can be phrased as an instruction to it. The approval card is what stands between such a sentence and a change made under your name. Approve a card once and the action runs once, so a dropped connection cannot produce the same work item twice. A written change then behaves exactly as if you had made it yourself: version history, notifications, mentions and the activity feed all record it under your name.

​

When it cannot find something

If a search comes back empty, it says so and names what it looked for. It does not guess. If you name a space or a project it has not seen, it lists the ones you do have rather than inventing a match.

---

​

Conversation history

Chats are saved as you go. Open the history icon in the panel header to see your earlier conversations, each with a short title taken from your opening question. Click one to reopen it exactly as it was, including the result cards. Delete any chat from the same list.

---

​

Privacy

Chat transcripts are unusually revealing. They hold what you were unsure about, what you were planning, and quotes from whatever you had open. Collabase treats them accordingly.

---

​

Limits worth knowing

• A single question scans at most 100 spaces and 200 projects. On very large instances, narrow the question to a space or project by name.
• A registry search without a named schema or type looks through at most 50 object types, and resolves at most 10 relations per object to their names.
• Lists come back in pages of 10, up to 25 at a time. Ask for more, or narrow the search, if the item you want is not there.
• History and discussion are read 20 entries at a time, newest first.
• The “what happened” digest looks back at most 90 days and returns at most 25 entries per category.
• A status move only offers the statuses the item’s workflow actually allows from where it stands. If the one you want is not on the list, the workflow does not permit that step from here.

---

​

Next steps