Managing access to admin copilot

Who may use it. Access here means proposing changes to configuration, so the list should be short.

Who may use it. Access here means proposing changes to configuration, so the list should be short.

Set it

1. Open the AI settings in Admin Center.
2. Set who may use admin copilot.
3. Assign it to the people who already administer the account.
4. Review the list after any team change.

It follows existing permissions

Somebody can only change what their role already allows. Admin copilot makes configuration easier to reach, not broader.

That is the reassuring part, and it is also why the underlying roles need to be right first.

Give it to your admins, not more widely

The temptation is to let more people self-serve because it is now easier. Configuration changes affect everybody, and the constraint that stops the account becoming unmanageable is how many people are making changes, not how hard the changes are to make.

Easier is not the same as safer

Somebody who could not previously build a trigger also could not previously build a bad one. Keep the review habits you already had.

Log what changes

Whatever your team already does to record configuration changes should cover changes made this way. A change nobody can trace is the expensive kind, however it was made.

Where it does widen usefully

A team lead who understands the process but not the interface can now describe what is needed. That is a real gain, and it works best as a proposal they hand to an admin rather than as direct access.

See also

• What admin copilot does
• Creating custom roles
• Testing admin copilot changes before applying them