Capabilities
Workspace
A workspace is where work in MAIA lives. It holds your team, your projects, and what MAIA has learned about your business, and each project's owner decides who else can see it.
How the pieces relate#
A workspace holds people, credits, and projects. A project holds the layers, the views, the chat, and its own memory. Personal and workspace skills and knowledge sit beside the projects, so what you save at those levels is there in the next project. Project memory stays with its project.
Sharing works in two ranges: inside the workspace and outside it. Inside, you set a project's access level and your colleagues open it as themselves. Outside, you send a link, and the viewer sees the map and the table without the researched values or the contacts.
What is shared and what stays private#
A workspace shares by choice. A project starts private, and you open it up.
| Thing | Who can see it |
|---|---|
| A project | Who can see itOnly you, until you set its access to Can view or Can edit |
| Project memory | Who can see itEveryone who can open the project |
| A workspace skill | Who can see itEveryone in the workspace |
| A personal skill | Who can see itOnly you |
| Workspace knowledge | Who can see itEveryone in the workspace. MAIA reads it in their conversations too |
| Personal knowledge | Who can see itOnly you |
| Favorites | Who can see itOnly you |
| Credits | Who can see itEveryone in the workspace. Any member's chat and enrichments spend from the one balance |
| A shared link | Who can see itAnyone who has it, until it expires or you revoke it. A gated link asks for a work email first |
Note
Credits are one balance. A colleague's enrichment run spends the credits you bought. See Credits.
Where to find it#
| You want | Read |
|---|---|
| Your team in the same projects, skills, and knowledge | ReadShared workspaces |
| A project in the hands of someone outside your team | ReadSharing and publishing |
| A table you can take into another tool | ReadExport |
In the app, the workspace's name and members are under your account, on the Workspace tab. A project's access level is set from its Share dialog. Over MCP, list_projects returns the projects you can open.
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. One workspace cannot read another's. More on how your data is handled: Data and privacy.
Related#
In this section
- Shared workspacesA 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.
- Sharing and publishingMAIA's sharing takes a project and returns a link you can send to anyone, with or without a MAIA account. Export takes a layer and returns a spreadsheet.