> ## Documentation Index > Fetch the complete documentation index at: https://docs.collabase.ch/llms.txt > Use this file to discover all available pages before exploring further. > The assistant built into Collabase. Ask it about your work, and let it create and change pages, whiteboards and work items for you. # 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. On screen, CollabaseAI calls tasks **work items** and sprints **cycles**. Both are the same things documented under [Projects](/projects/tasks) and [Sprints](/projects/sprints). *** ## 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. | Action | How | | ------------------------------ | ---------------------------------------------------------------------------------------------------- | | **Open or close the panel** | Click the CollabaseAI mark in the dock, or press `Cmd` + `J` (macOS) / `Ctrl` + `J` (Windows, Linux) | | **Start a fresh conversation** | Click the refresh icon in the panel header | | **Open saved chats** | Click the history icon in the panel header | | **Close the panel** | Click the close icon, or press the shortcut again | If the launcher is not there, an administrator has not enabled AI on this instance yet. See [AI Configuration](/admin/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. | Where you are | What the chips offer | | ----------------------------- | -------------------------------------------------------------------------------- | | Anywhere else in the platform | Your open work items, what happened in the last two weeks, what is due soon | | On a work item | What changed on this item, a summary of the discussion, where the item stands | | On a page | A summary of the page, the to-dos hidden in it, an explanation of the terms used | | On a Registry object | A summary of the Object, what it is linked to | ### 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. Work items, pages, cycles, discussions, Registry objects and test runs, across every space you can access, including their history. Create work items, pages, whiteboards and Registry objects, change fields, move an item to another status or another project, and write comments. Each one waits for your approval. A digest of what moved while you were away, and the review numbers for a finished cycle. What is assigned to you, what is due, what a cycle delivered against what it committed to, and whether a release milestone is ready. Every skill it has, with an example of how to ask for it, is listed in the [skill reference](/concepts/collabase-ai-skills). ### 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. Saved chats are kept for **30 days** and then deleted for good. This is a fixed window on every Collabase instance. *** ## 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. | | | | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Who can read your chats** | Only you. There is no sharing option and no administrator view. | | **What CollabaseAI can see** | Exactly what you can see. It resolves your permissions per space, per project and per page, including pages with restricted access. | | **How long chats are kept** | 30 days, then deleted. Deleting your account deletes your chats with it. | | **Where the text is processed** | With the AI provider your administrator configured. On a self-hosted provider, nothing leaves your infrastructure. See [AI Configuration](/admin/ai-configuration). | *** ## 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 Every skill CollabaseAI has, with an example of how to ask for it. For administrators: connecting a provider and enabling semantic search.