Permissions and Visibility

Visibility controls who can find and use an AI teammate. Permissions control what the teammate can access once it is working.

Visibility types

Type	Use when
Public teammate	The teammate should be discoverable and usable by people in the workspace.
Private teammate	The teammate should be limited to selected people or a smaller group.
Sidekick	The teammate is personal to one user and should use that person’s private context.

Connector permissions

Visibility does not automatically grant every connected integration. Personal and organization-level integrations can be connected globally in Type, but a teammate should only get the integrations assigned to its role.

Keep sensitive systems narrow:

• Give a teammate only the connected integrations it needs for its role.
• Avoid putting secrets in instructions or thread messages.
• Use a private teammate or Sidekick when the work depends on personal or sensitive context.

Thread access

Threads inherit the access model of the surface they belong to. A thread in a shared teammate is visible to people with access to that teammate. A Sidekick thread is private to the Sidekick owner.

Changing access later

You can adjust teammate visibility and membership from teammate settings. When changing access, review connectors, skills, tasks, and open threads so the teammate’s role still matches who can see it.