A single-player AI chat tool is useful; a team AI platform is transformative. When everyone on your team works in the same shared workspace — accessing the same agents, building on the same prompts, reviewing the same conversation history — your collective AI capability compounds. This post walks through the collaboration features in The Chat Agent: how to set up a team workspace, invite members, manage permissions, share assets, and grant read-only access to specific conversations.

Creating a team workspace

When you sign up, you start in a personal workspace. To bring in colleagues, head to Settings → Teams and create a team. Give it a name — your company or department — and you'll land in the team dashboard: a shared space where all members can see and contribute to the team's library of agents, prompts, workflows, and dynamic tools.

Every team member's personal workspace stays private. The team workspace is what you explicitly choose to collaborate in, so there is no risk of accidentally exposing a half-finished experiment to the whole team.

Inviting members

From the team dashboard, click Invite members and enter email addresses. Each invitee receives a sign-up link — or, if they already have an account, a join notification in the app. Invitations are tracked in the Members tab so you can see who has accepted and resend to anyone who missed the email.

Seat availability depends on your plan. See Pricing for the member limits on each tier and how to upgrade.

Roles and permissions

The Chat Agent uses a simple three-role permissions model per workspace:

Owner — full control: billing, member management, all team content, and provider integrations.
Admin — can manage members and all shared content; cannot change billing or delete the workspace.
Member — can create and use shared agents, prompts, workflows, and tools; cannot manage membership or billing.

Roles are scoped to a single workspace, so the same person can be an Admin in your engineering team and a Member in a second workspace. Full details are in the Teams documentation.

Sharing agents, prompts, and workflows

Any asset you create inside the team workspace is automatically visible to every member at your role level or above. Assets you create in your personal workspace stay private until you explicitly move or copy them to the team.

This separation matters in practice: you can iterate privately on a new agent definition or prompt template, refine it over several sessions, and only promote it to the team library once it is ready. The team library then becomes a curated collection that the whole team can rely on — not a dumping ground for half-finished experiments.

The same principle applies to workflows: build and test a multi-step agent workflow in your own workspace, then publish it to the team with a single click. Team members can run it immediately from the workflow catalogue, with no additional setup.

Sharing individual conversations

Sometimes you want to share the output of a specific conversation — a research summary, a drafted document, a data analysis — without granting access to the whole workspace. For this, The Chat Agent supports read-only conversation sharing.

Open any conversation, click the Share button, and choose Anyone with the link. The link recipient sees the full conversation thread — including any inline tool-call traces — in a clean, read-only view. They do not need an account, and they cannot send messages or modify anything.

Read-only links are useful for:

Sharing AI-generated research with a stakeholder who does not need their own account.
Attaching a conversation to a document or project tool as supporting evidence.
Archiving a completed analysis for future reference.

You can revoke the link at any time from the conversation's share settings. Once revoked, the URL returns a 404 and no cached version is served. See Sharing documentation for details on revocation.

What is shared vs. what stays private

To summarise the visibility model at a glance:

Personal chats — private to your own workspace.
Team agents, prompts, workflows, and tools — visible to all team members as soon as they are created in the team context.
Shared conversation links — accessible to anyone with the link, in read-only mode, until revoked.

Keep reading

For the full reference on team features, start here:

Teams documentation — workspace setup, member management, roles, and plan limits in detail.
Sharing documentation — read-only conversation links and how to revoke access.
Team collaboration overview — a feature-level summary of every collaboration capability in the platform.

Collaborating with Your Team on The Chat Agent