Admin overview

You need the org_admin role. Everything below lives under Admin.

The control model in one picture

Lucy decides what is allowed by layering four levels. At every layer, the stricter setting wins, so nobody can loosen what a level above them has tightened.

flowchart LR
  A["Contract"] --> B["Organisation"] --> C["Groups and people"] --> D["Conversation"]

• Contract sets the outer limit: sandbox yes or no, memory yes or no, file size, monthly ceiling.
• Organisation settings are yours. Sensitive features default to off.
• Groups and people can be granted a feature (web search, models, agents) or given their own limits.
• People and conversations may tighten their own settings, such as shorter retention or turning web search off, never loosen them.

This is why you can switch a capability on for a pilot group with confidence: it cannot spread past the people you named.

Recommended order

1. Sign-in: connect your identity provider and prove your domains.
2. Members, groups and roles: decide who administers and who audits.
3. Rules: write the policy Lucy follows for everyone.
4. Data retention and Sandbox: set how long data lives and what code may reach.
5. Limits and budgets: protect your spend before people arrive.
6. Models, Memory, Agents: switch on capability deliberately.
7. Connectors: enable the integrations you need, with approvals.
8. Audit log: confirm you can see what happens, then invite everyone.

Start from a baseline

Not sure where to begin? Recommended configurations gives you three ready-made profiles (strict, balanced, open) with every setting spelled out.

Recommended configurationsStrict, balanced and open profiles, setting by setting.

Security view of the settingsWhich settings reduce which risks.