Plan requirement
| Subscription | Suite Professional or higher, Support Professional or higher |
| Access | Admin |
Three things decide how this is handled: only the account owner can manage the account-wide setting, conversational assistance is on by default for admins on the standard Admin role, and admin copilot itself does not need the Copilot add-on.
Set it
- In Admin Center, click the AI icon in the sidebar.
- Select Admin copilot, then Admin copilot.
- Set Allow conversational assistance.
- Review it after any change to who administers the account.
An ordinary admin cannot change this switch, so an afternoon of looking will not find it. If you need it changed, the account owner is who to ask. On Enterprise there is a second, narrower control that admins do hold; that is further down.
What the add-on does and does not gate
Admin copilot is included from Suite Professional upwards. The Copilot add-on is only needed for it to make recommendations about Copilot-specific features such as auto assist and intelligent triage.
So without the add-on you still get admin copilot; you get fewer things it can recommend about.
What you are enabling
Admin copilot has three parts: Latest insights, Top recommendations and Conversational assistance. The setting above governs the third, which is the one that creates and updates configuration.
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.
On by default is a decision you inherit
Because conversational assistance starts on for standard admins, the shape of your access list is whatever your admin list already is. If that list grew over the years for reasons unrelated to configuration, this is a good moment to read it.
On Enterprise there is a finer control. Account admins can decide per custom role whether conversational assistance is available, from the custom roles themselves rather than from this page. So an account with custom roles can leave the feature on and still narrow it, which is the better answer than reading a long admin list once and hoping.
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.
Comments
0 comments
Article is closed for comments.