Workspaces and membership

Understand how invitations, membership and delegated access shape collaboration.

A Workspace is the team boundary

Each Workspace has its own members, Projects and delegated access. Membership comes from an invitation. Sharing a Host, repository or provider account does not grant Workspace membership. A person may belong to more than one Workspace, and each one remains separate.

Invitations and prepared Projects

An administrator invites collaborators and grants access to the relevant Project. A prepared Project can provide an execution environment so invited members can begin work without pairing their own computer or signing into an AI provider. Administrators decide which execution and integration access to delegate.

Access follows the work

Project and Task access controls who can read or change shared work. Private conversations retain their own access rules. Workspace membership does not make every private Session visible, and a shared Task is not a public link.

When to create a new boundary

Use a Workspace for a distinct team or tenant. Use a Project for a continuing topic, product area or repository. Use Tasks for concrete objectives within that context. Ask an administrator to review access when someone joins, changes roles or leaves.