Skip to main content
When conversation sharing is on in your workspace, a conversation only opens for the people, groups, and API keys it’s shared with. The API follows the same rule. Pods are the place to work together with several people, agents, and API keys. Conversations in a Pod aren’t affected: they still open for whoever can access the Pod.

​
Who can open what

A conversation that isn’t shared with the caller returns 403 with conversation_not_shared.

​
Share a conversation

Groups are matched by their exact name. Workspace is everyone in the workspace, API keys included.

​
Find the integrations to update

  1. In your workspace admin, go to Developers → API keys. Keys with the Admin scope keep working as before.
  2. For each other key with a recent Last used date, check whether its integration opens conversations it didn’t create. For example, a conversation ID copied from Dust, received from a webhook, or created with another key. Click a key to see the conversations it ran agents in, by credits or by latest activity.
  3. For those integrations, create the conversation with the same key and add people with sharedWith, or switch to a key with the Admin scope.
Your audit logs show every access that bypasses sharing: each time a key with the Admin scope opens a conversation that isn’t shared with it, they record a conversation.admin_access_granted event.