Workspace
Workspaces keep your team and AI on the same page.
Shared folders, agents, computers, and chats: one container.
Four roles. Pick what fits.
Give people the right amount of access. Bump them up later if needed.
Runs the show. Handles billing and can wind the workspace down. One per workspace.
Invites people, sets up shared things. Doesn't touch the bill.
Joins in. Creates files, agents, chats. Can't add or remove other people.
Reads what's in the workspace but can't change anything. Great for stakeholders.
Each person has their own idapt subscription, and what they do gets charged to them. Sharing a workspace is about access, not paying for someone else.
What you get
Files, agents, computers, chats: all under one workspace. No more 'which Slack channel was that in'.
Viewer, member, admin, owner: each role maps to real permissions across resources.
Flip the visibility and your workspace gets a public URL: perfect for open research or shared playbooks.
Not everything needs to be workspace-wide. Share a single file, agent, or chat with a specific person.
Who it's for
One workspace per workstream. Members hit one URL and see the agents, files, and history that belong to it.
Public workspace surfaces your docs, your agents, and the chats that built them: your community can clone.
One workspace per engagement. Hand it over at the end, keep nothing tangled.
How it works
- 1Create a workspace
Name it, drop in the folders that belong to it.
- 2Invite members
Pick roles. Members see only what their role grants.
- 3Hand off chats and agents
Move a chat into the workspace; agents created inside it inherit workspace scope.
- 4Ship or share
Keep it private, share with specific people, or flip the workspace public and let the world see it.
Frequently asked
Make space for your team.
Invite people, drop in your folders, and get going together.