Using Space Sharing and safety
Import and export
Back up your setup, move it between workspaces, or hand a team's tools to another team in one file.
Built something useful, such as agents, playbooks, tables and tools? You can pack it into one file and bring it into another workspace, a colleague's account or a team.
Find both under Settings › Export and Settings › Import.
Exporting
- Open Settings › Export.
- Choose where from:
- My resources: everything you own.
- A team (group): everything that group owns. Any member can export it.
- Tick what you want: individual items, a whole kind, or everything.
- Download the file.
What can be exported
Tables, skills, API tools, MCP servers, Functions (including their bundled libraries), knowledge bases, pages, agents and playbooks.
What is not exported
| Not included | Why |
|---|---|
| Your Front Desk | It's personal to you |
| App connections and channels | They're accounts with secrets, not definitions |
| Files and documents inside knowledge bases | That's your data, not the setup |
| An agent's memory | It's what it learned about its people |
| One-off playbooks created for a single request | They don't last |
| Credentials and secrets | Never exported |
Only what you can see is exported.
Importing
- Open Settings › Import and choose the file.
- Space shows a preview: what would be created and which references can't be found in your workspace. Nothing is created yet.
- Choose where to import: My resources, or a group you administer.
- Confirm.
Imports are always new copies
Importing never overwrites anything. Each item is created as a new copy, checked as if you'd made it by hand, with the same limits and rules. Links between items (an agent that uses a playbook) are reconnected to the new copies automatically.
- If a copied agent's handle is taken, it becomes
@name-2. - References to things outside the file, such as a knowledge base that doesn't exist here, are kept if you can use them, and dropped otherwise. The result lists these under To check. A playbook with missing pieces is imported as a draft.
- All or nothing. If any item can't be created, you're told which one, and nothing is kept.
After importing, reconnect anything that needed secrets: tool credentials, integration sign-ins, Function secrets. Then re-run Check on imported playbooks.
Developers
The MCP server can export and import the same files programmatically. See What it can do.