Do team members get charged separately?

Each member needs their own idapt subscription: every paid action is billed against the subscriber who runs it. Workspace sharing is access control, not seat pooling.

Can a workspace be public on the web?

No. Publishing is per resource, not per workspace: files, chats, and agents each get their own share link. Everything else in the workspace stays private.

Can I move an existing chat into a workspace?

Yes. move a chat at any point and the conversation history, agents, and files attached to it follow.

Workspace

Workspaces keep your team and AI on the same page.

Shared folders, agents, computers, and chats: one container.

Use for Free See pricing

Four roles. Pick what fits.

Give people the right amount of access. Bump them up later if needed.

Owner

Runs the show. Handles billing and can wind the workspace down. One per workspace.

Admin

Invites people, sets up shared things. Doesn't touch the bill.

Member

Joins in. Creates files, agents, chats. Can't add or remove other people.

Guest

Reads what's in the workspace but can't change anything. Great for stakeholders.

A note on billing

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

Everything in one container

Files, agents, computers, chats: all under one workspace. No more 'which Slack channel was that in'.

Roles that actually scope

Viewer, member, admin, owner: each role maps to real permissions across resources.

Per-resource sharing

Share a single file, chat, agent, app, or repo with a specific person, or with anyone holding the link.

Publish to the Hub

Publish a chat, an app, or a template to the Hub when you want it found. The workspace around it stays private.

How it works

1
Create a workspace
Name it, drop in the folders that belong to it.
2
Invite members
Pick roles. Members see only what their role grants.
3
Hand off chats and agents
Move a chat into the workspace; agents created inside it inherit workspace scope.
4
Ship or share
Keep it private, share with specific people, or publish the individual chats, files, and apps you want public.

Frequently asked

Make space for your team.

Invite people, drop in your folders, and get going together.

Create a workspace Read the docs

Read the docs

Pair with

What you get

Everything in one container

Files, agents, computers, chats: all under one workspace. No more 'which Slack channel was that in'.

Roles that actually scope

Viewer, member, admin, owner: each role maps to real permissions across resources.

Per-resource sharing

Share a single file, chat, agent, app, or repo with a specific person, or with anyone holding the link.

Publish to the Hub

Publish a chat, an app, or a template to the Hub when you want it found. The workspace around it stays private.

How it works

Create a workspace

Name it, drop in the folders that belong to it.

Invite members

Pick roles. Members see only what their role grants.

Hand off chats and agents

Move a chat into the workspace; agents created inside it inherit workspace scope.

Ship or share

Keep it private, share with specific people, or publish the individual chats, files, and apps you want public.