Team Settings¶
Open Chat Studio (OCS) 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 Settings is organized into sections:
- Integrations — configure and manage the external services your chatbots use: LLM & embedding, Speech, Messaging, Authentication, and Tracing providers.
- Members — invite people to the team, and manage their roles and access.
- Developers — manage Custom Actions and OAuth applications for extending and integrating with your chatbots.
- Data — export your team's files, and migrate the team to another OCS instance.
- Feature Flags — where Team Admins turn experimental features on or off for the team.
Integrations¶
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
- MCP (only visible on teams with that feature enabled)
A single Add integration button connects a new provider in any category.
Every provider's edit page also has a Usages tab, showing everywhere in your team that provider is referenced — see Find Where a Provider Is Used.
Members¶
The Members & access section lists everyone with access to your team, active members and pending invitations together in one table. Team Admins invite people, assign them roles, and remove access from there.
Developers¶
The Developers section groups the tools for extending OCS: Custom Actions, which let a chatbot call an external HTTP service (setup steps are in the Custom Action Tech Hub Guide), and OAuth applications, which let external systems read or write your team's data through the API.
Data & Migration¶
The Data & Migration section lets Team Admins export the team's files, register a migration public key, and delete the team. This section is only visible to Team Admins. See Migrate a Team to Another Instance for the full walkthrough of moving a team — its chatbots, configuration, and chat history — to a different OCS server.
See also¶
- Integrations
- Members & access
- Developers — Custom Actions and OAuth applications
- Data & Migration — export team files and migrate to another instance
- Feature Flags — experimental features your team can turn on
- User Groups