Capabilities/Workspace
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.
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 to add a colleague.
| Role | What it can do |
|---|---|
| Admin | What it can doWorkspace settings, such as a database connection, on top of an editor's or a viewer's rights |
| Editor | What it can doEdit any project set to Can edit, and change workspace skills and knowledge |
| Viewer | What it can doOpen 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.
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 | Who can open itOnly you | Who can edit itOnly you |
| Can view | Who can open itEveryone in the workspace | Who can edit itOnly you |
| Can edit | Who can open itEveryone in the workspace | Who can edit itEditors and admins in the workspace |
To change the level:
- Open the project's menu and choose Share.
- Choose Workspace members.
- 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.
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 | How it is usedAnyone in the workspace can run them. Editors and admins can change them |
| Workspace knowledge | How it is usedMAIA reads it in every member's conversations |
| Credits | How it is usedChat and enrichments spend from one workspace balance |
| Projects set to Can view or Can edit | How it is usedThey appear on the Workspace tab of the projects page |
What stays with you#
| Stays with you | Why |
|---|---|
| Favorites | WhyThe rows you star are your own shortlist |
| Personal skills | WhyA method you have not chosen to share |
| Personal knowledge | WhyContext about you, not about the company |
| Private projects | WhyWork you have not opened to the workspace |
To share a personal skill, save it to the workspace. See 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.
In the app and over MCP#
| Where | How |
|---|---|
| The web app | HowOpen Share on a project and choose an access level |
| MCP | Howlist_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 covers people outside the workspace.
- Knowledge explains the three levels of what MAIA remembers.