# Shared workspaces

A shared workspace in MAIA puts a team in the same projects, skills, and knowledge. Each project starts private, and its owner decides whether the workspace can view it or edit it.

Updated: 2026-09-30. Source: https://maia-analytics.com/docs/capabilities/shared-workspaces

## What it answers

Research done alone gets done twice. A shared workspace lets a colleague open your project, run your skill, and work from the context MAIA already has about your business.

## Roles

Every member has one role. To see roles, open your account, then the **Workspace** tab. MAIA sets roles when it adds members, and it adds them on request: there is no invite button, so ask [support](mailto:support@maia-analytics.com) to add a colleague.

| Role | What it can do |
| --- | --- |
| Admin | Workspace settings, such as a database connection, on top of an editor's or a viewer's rights |
| Editor | Edit any project set to **Can edit**, and change workspace skills and knowledge |
| Viewer | Open projects set to **Can view** or **Can edit**. Cannot edit either |

A role is about projects, skills, and knowledge. It does not gate spending: any member can buy credits, and any member's runs spend from the workspace's balance. See [Buy credits and auto-reload](https://maia-analytics.com/docs/billing/buy-credits).

## Open a project to the workspace

A project has one of three access levels. A new project starts at **No access**, which the projects page shows as Private.

| Level | Who can open it | Who can edit it |
| --- | --- | --- |
| No access | Only you | Only you |
| Can view | Everyone in the workspace | Only you |
| Can edit | Everyone in the workspace | Editors and admins in the workspace |

To change the level:

1. Open the project's menu and choose **Share**.
2. Choose **Workspace members**.
3. Under **Project access**, pick **Can view** or **Can edit**, and choose **Save**. The project appears on the **Workspace** tab of the projects page for everyone in the workspace.

> **Note:** Before you choose **Can edit**: a project has one chat, and MAIA answers one request at a time, so two people cannot dispatch work in it at once. A colleague's runs spend the workspace's credits. Everyone who can open the project can also read its project memory.

![The Share with workspace dialog. Under Project access, a dropdown lists No access, Can view, and Can edit, each with a one-line description of who can open and edit the project.](https://maia-analytics.com/product-shots/docs/share-access-levels@2x.png)

The three access levels, from the project's Share dialog.

A project set to **Can view** has no chat for anyone but its owner. Colleagues read it. They cannot dispatch work in it.

## What the workspace shares

| Shared | How it is used |
| --- | --- |
| Workspace skills | Anyone in the workspace can run them. Editors and admins can change them |
| Workspace knowledge | MAIA reads it in every member's conversations |
| Credits | Chat and enrichments spend from one workspace balance |
| Projects set to **Can view** or **Can edit** | They appear on the **Workspace** tab of the projects page |

## What stays with you

| Stays with you | Why |
| --- | --- |
| Favorites | The rows you star are your own shortlist |
| Personal skills | A method you have not chosen to share |
| Personal knowledge | Context about you, not about the company |
| Private projects | Work you have not opened to the workspace |

To share a personal skill, save it to the workspace. See [Skills](https://maia-analytics.com/docs/capabilities/skills).

## Isolation

Each workspace is isolated. Your layers, uploads, and synced tables live in a database instance that belongs to your workspace alone, and the agent's queries run there with access to that project only. Projects, chat, skills, and knowledge are stored per workspace, and every read is scoped to yours. See [Data and privacy](https://maia-analytics.com/docs/reference/data-and-privacy).

## In the app and over MCP

| Where | How |
| --- | --- |
| The web app | Open **Share** on a project and choose an access level |
| MCP | `list_projects` returns the projects you can open, including those shared with you. `send_message` works only on a project you can edit. Access levels are set in the web app |

## Related

- [Sharing and publishing](https://maia-analytics.com/docs/capabilities/sharing-and-publishing) covers people outside the workspace.
- [Knowledge](https://maia-analytics.com/docs/capabilities/knowledge) explains the three levels of what MAIA remembers.