Common Avvi messages and what they mean
The messages people ask about most, what each actually means, and which of them you can do something about.
Most messages fall into three groups: something about your access, something about the client’s setup, or something about a limit.
Knowing which group a message belongs to is usually enough to know who fixes it. Access messages are about you, setup messages are about the client, and limit messages are about time.
The table names each message, what it means, and who acts.
| Message | What it means | Who acts |
|---|---|---|
| “You do not have permission to perform this action. Please contact your administrator for access.” | Your account is not allowed to do that. The specific permission is deliberately not named | Your master administrator, in your access group |
| “Multi-tenant chat is not enabled for your organization” | The organisation-wide switch for working on clients is off | Your master administrator, in settings |
| “Your MSP organization has no access groups configured.” | No access groups exist at all, so nobody but the master administrator can get in. The rest of the message varies with where you hit it, for example “before you can log in” or “before you can use the AI chat” | Your master administrator |
| “Your account does not have multi-tenant access permission.” | Groups exist and yours does not grant client access | Your master administrator |
| “Your IP address is not authorized to access this resource. Please contact your administrator.” | An address allowlist is on and yours is not on it | Whoever manages the allowlist, or Avvi support if everyone is locked out |
| “I am unable to reach the on-premises connector” | The client’s connector is not checking in. The request failed rather than queued | Whoever can get to that machine |
| “No available licenses for” a subscription | Every seat is taken, or a newly bought seat has not appeared yet | You, by freeing one or buying more |
| “Daily API limit reached for this client” | That client has used its daily allowance. It resets at midnight UTC | You, by raising the cap, or by waiting |
| “No exact match for” a name, with suggestions | The search found near matches rather than the person | You, by picking one or using an email address |
| “No users found matching” a name “within your authorized scope” | Nobody matching is visible to your account. The person may still exist | Your master administrator, if you should be able to see them |
Good to know
A user quoting a technical-looking message they do not understand is usually quoting one of these.
The permission message never names the permission. That is deliberate, and it means the fix is a conversation with whoever manages your access groups rather than a hunt.
Two of these look alike and are not. No access groups configured affects everybody; no multi-tenant permission affects one person.
Several of these arrive with a cross symbol in front of them. Searching on the words rather than the whole line is the reliable way to match one.
Related pages
Refusals, connector problems, licence shortages and address allowlists each have their own page with the full remedy.