Skip to content

Team Settings

Open Chat Studio supports multiple organizations/departments working in the same system while keeping their data completely separate. Each organization is called a Team. Teams have their own settings, private data, and chatbots.

As an OCS user, you can belong to several teams at once, with different roles in each — for example, an Admin on one team and a Viewer on another. Roles are managed with User Groups.

Team configuration

Global settings are managed at the Team level, from the Integrations page. It lists every external service provider your team has connected, as rows in a single table you can filter by category:

  • LLM & embedding
  • Speech
  • Messaging
  • Authentication
  • Tracing

A single Add integration button connects a new provider in any category.

Finding where a provider is used

Every provider's edit page has a Usages tab. Opening it lists everything in your team that references that provider.

  • Chatbots — links go to the working version's edit page; references belonging to a published version are tagged with a version badge.
  • Pipelines — rolled up to their owning chatbot. Archived pipelines are included.
  • Channels — rolled up to their owning chatbot.
  • Collections — rolled up to the owning collection.
  • Evaluators — LLM evaluators that use the provider, for LLM service providers.

This is most useful before rotating an API key, deprecating a provider, or triaging a potentially leaked credential — it gives you an immediate picture of what would be affected.

Moving a team to another instance

To move a team — its chatbots, configuration, and chat history — to a different OCS server, see Migrate a Team to Another Instance.

See also