The different kinds of Avvi user
Five kinds in two groups: people at your organisation, and people at your clients. What each can do comes from a different place in Avvi.
Avvi users fall into two groups: people at your own organisation, who work across clients, and people at a client, who work within their own company.
Within each group, what somebody can do comes from a different place. Your own administrators get it from an access group you control. A client’s staff get it from a mapping you set on that client.
Knowing which group somebody is in tells you where to look when they cannot do something.
| Kind | Belongs to | What they can do comes from |
|---|---|---|
| Master administrator | Your organisation | Full access, held automatically by whoever set the organisation up, and not removable |
| MSP administrator | Your organisation | The access group they are in. A group with the Avvi Master Admin toggle reaches the same as the master administrator |
| Client administrator | A client | A mapping you set on that client, covering the user groups they manage |
| Client user | A client | A mapping you set on that client, for their own group |
| Avvi support | Avvi | A grant you create for portal access, plus a separate audited route Avvi can open itself to investigate a conversation |
Good to know
Your organisation has one master administrator, and the product picks the holder rather than you.
The holder is whoever completed the setup first. That access cannot be removed afterwards.
Master administrator is not a tier above MSP administrator. An access group with the Avvi Master Admin toggle reaches the same things.
The one difference by default is tenant-wide security investigation. A group has to be granted that separately.
A client administrator manages other people within their own company. A client user manages their own account and equipment.
Related pages
What the master administrator can do, giving a client’s staff access, and turning on a feature for one of their groups each have their own page.