Reference
Rollout checklist
What an IT team prepares before inviting the whole company: sign-in, people and groups, models and spending, the rules Bots work within, and how data is kept. Print it and tick it off; each line names the admin console section where it is done.
1. Sign-inCopy link to this section
- Identity providers: register your SAML or OpenID Connect provider and run a test sign-in before anyone depends on it.
- Enterprise controls: decide whether single sign-on is required for everyone, and connect directory provisioning if your directory supports it.
- Sign-in security: set idle sign-out, when people must sign in again, and time-limited administrators.
See Single sign-on and Directory provisioning.
2. People and groupsCopy link to this section
- Groups: agree group names with the teams that will use them, and name each group's administrators.
- New members: write the welcome message and choose the Bots new members find from the start.
- Brand: set the workspace's name, colours and logo, so people recognise it at their first sign-in.
- People: name at least two administrators, then invite a small pilot group before everyone else.
3. Models and spendingCopy link to this section
- Credentials: add the keys for the model providers you have chosen.
- Usage: set monthly spending caps, and the prices costs are estimated with.
- System status: confirm stored secrets are on the current encryption key and the model providers answer.
See Model providers and Budgets and cost control.
4. The rules Bots work withinCopy link to this section
- Boundaries: write the rules a Bot may never break, such as paying or deleting without a person.
- Enterprise controls: choose what each role and group may use, the network policy for Bot computers, and the models people may pick.
- Plugins: connect only the services Bots need, and choose which Bots may reach each one.
- Company context: give every Bot a short company profile and a glossary of your own terms.
5. Records and dataCopy link to this section
- Audit: agree who reads the audit trail and how often, and try an export.
- Webhooks: if your security team collects events, send audit events to their system.
- Privacy: decide who handles a person's request to export or erase their data.
- Read how backup and restore work, and agree who to ask if something must be restored.
6. Before the wider launchCopy link to this section
- Announcements: post a banner telling people where to start and where to ask for help.
- Alerts: check that nothing needs an administrator, and choose how you hear about new alerts.
- Your first month: follow who joined and what the Bots did, and what to do next.
Tip
The admin quick reference lists where the everyday administrator tasks live once the workspace is running.
Last updated