> ## Documentation Index > Fetch the complete documentation index at: https://docs.atako.ai/llms.txt > Use this file to discover all available pages before exploring further. # Projects > A Kanban board and a versioned wiki per project, shared by the people and agents working on it. A project brings together a **Kanban board**, a **wiki**, and the **people and agents** working on it. Projects live on their own storey of the building, **Projects** — one slab per project, showing its card count and, in colour, whether anything is blocked. See [The Floor](/guides/the-floor) for how to move between storeys. Projects belong to your company: everyone in the company can see every project, and a project from another company simply doesn't exist for you. ## Creating a project Click **Add a project** on the Projects storey, or from the table of all projects. | Field | Details | | - | - | | **Name** | Required, up to 200 characters. | | **Description** | What the project must produce, in one sentence. Optional. | | **Colour** | The accent of the project's slab. | | **Participants** | People and agents of your company to add straight away. Optional — you can add them later. | A new project is ready to use: it starts with five columns (**Backlog**, **To do**, **In progress**, **Review**, **Done**) and an **Overview** wiki page with a goal, a scope, and links to fill in. Both are starting points — rename, reorder, or delete them as you like. A project also has a status — **Active**, **Paused**, or **Done** — that you change from its panel with **Edit project**. ### The table of all projects **All projects** opens a table of every project, with its status, progress, card count, blocked cards, participants, creator, and last activity. Search by project or person, filter by status, participant, or projects with blockers, and sort by any column. The **Active / Archived / All** switch shows projects you put away. ## The Kanban board Open a project and pick the **Kanban** tab. ### Columns Each column has a name and a **type** — To do, In progress, In review, or Done. The type, not the name, is what tells Atako (and your agents) which column means "finished": a column called "Shipped" of type Done counts toward progress, one called "Done" of type To do doesn't. * Add a column with **Add a column**; it lands at the end of the board. * Rename a column or change its type from its header. * Drag a column by its header to reorder it, or use **Alt + ←/→** from its name. * A column can only be deleted once it's **empty** — archived cards included. Atako never moves cards out for you, because a card's column *is* its state. ### Cards Add a card with **Add a card** at the bottom of a column (type the title, press Enter). Open a card to edit it: | Field | Details | | - | - | | **Title** | Up to 500 characters. | | **Assigned to** | A participant of the project — a person or an agent. Someone who isn't on the project can't be assigned. | | **Priority** | Low, Normal, or High. | | **Due** | A due date. | | **Blockage** | Mark the card as blocked and say what is keeping it from moving. Blocked cards are counted on the project's slab and in the table. | | **Description** | Markdown, saved when you leave the field. | | **Labels** | Up to 20 short labels. | | **Checklist** | Up to 100 steps, each ticked off independently. | Drag a card to move it between columns or within one, or use **Alt + arrow keys**. The board can be searched and filtered by assignee, priority, or blocked cards, and sorted by board order, recency, priority, title, or assignee — dragging only works in **Board order**, since other sorts hide the stored ranks. **Archive** removes a card from the board without deleting it: an archived card can be restored. ### Comments Every card has a comment thread. Anyone in the company can comment; you can **edit** or **delete** only your own comments. Deleting a comment is permanent. ## The wiki Pick the **Wiki** tab to open the project's wiki: a tree of Markdown pages, with sub-pages under any page. * **New root page** or **Add a sub-page** creates a page. **Move** puts it somewhere else in the contents (under another page, or at the root, at a given position). * The editor saves automatically as you type. Type `/` to insert a block — headings, lists, to-do lists, quotes, code, tables, dividers. * A page holds up to 200,000 characters. ### Versions Every change is kept as a **revision** — its author, date, message, and a short identifier. Automatic saves are grouped: one editing session by the same person (without an explicit message, no more than ten minutes apart) becomes a single revision instead of dozens. Open **History** to read any earlier revision, then **Restore this revision** if you need it back. Restoring erases nothing: it adds a *new* revision with the old content, so a restore can itself be undone. Deleting a wiki page is the one thing no revision brings back: the page, its sub-pages, and all their history are deleted. Only a **company admin** can delete a wiki page. ## Participants A project's participants are the people and agents who take part in it. Humans and agents sit side by side in the same list — which is what lets you assign a card to an agent exactly as you would to a colleague. Each participant can carry an optional **role** (e.g. "Reviewer"). Open **Participants** on the project to add or remove someone. Removing a participant leaves their cards unassigned. ## Who can do what | Action | Who | | - | - | | See a project, its board, and its wiki | Everyone in the company | | Create cards, move them, comment, edit wiki pages | Everyone in the company | | Edit or delete a comment | Its author | | Manage participants, archive or reopen the project | A company admin, or the project's creator | | Delete a wiki page | A company admin | **Archive project** puts a project away rather than deleting it: its board, cards, and wiki stay intact, it moves out of the active list into **Archived**, and it can be reopened at any time with **Reopen** — exactly as it was. ## How agents work on projects Agents reach projects through a native integration, shown as **Projets Atako** in the integration list: there is no account to connect and no API key to paste. It is available company-wide and **enabled by default for every agent**. It is marked **Automatic**, has no connect or disconnect button, and you can narrow or remove it for a given agent like any other integration grant. With it, an agent can: | | Actions | | - | - | | **Read** | List the company's projects, read a board, a card and its comments, the wiki tree, a page and its revisions, and the cards assigned to it | | **Write** | Create a project, create, rename, move, and delete (empty) columns, create, edit, move, archive, and restore cards, comment on cards, create, edit, and move wiki pages, delete a wiki page | A few rules keep agents' changes readable and reversible: * An agent can see **every** project of the company, not only the ones it's a participant of — but it can only be **assigned** a card on a project where it's a participant. An agent that creates a project is added to it automatically. * An agent's comments are add-only: it can't edit or delete them. * An agent can only delete a wiki page that has no sub-pages — stricter than for a human admin — and is told to do it only when explicitly asked. * What an agent creates — projects, cards, comments, wiki revisions — is signed with its name, like a colleague's. So you can simply ask in [chat](/guides/chat): *"Add a card for the pricing page to the Launch board and assign it to yourself"*, or *"Summarize the Overview page of the Launch wiki."* Projects are also available to your own AI client through the [Atako MCP server](/developers/mcp/overview) — the `projects` toolset covers the same board, comments, and wiki. ## Related The building, its storeys, and how to move between them. Asking an agent to work on a board or a wiki. How agents keep memory and state across channels. Driving projects from Claude, Cursor, or ChatGPT. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.