Why Avvi does not name the missing permission

The refusal hides the internal permission name, so describe the action you were trying to take rather than quoting the message.

Avvi refuses something and tells you to contact your administrator, without saying what to ask them for. That is deliberate rather than unhelpful, but it leaves you holding a message you cannot act on.

The way through is to describe what you were trying to do. Your administrator can find the right setting from that, which the message itself does not allow.

How it works

The refusal reads:

“You do not have permission to perform this action. Please contact your administrator for access.”

The message hides the internal name of the permission that is missing.

Most of the time it is generic and reads the same whatever was blocked. A few refusals do name the action or the feature.

Capabilities in Avvi are granted per user group rather than per person. A colleague in a different group can do things you cannot, which is why the same request works for them.

Good to know

Reading which of the two you got saves a round trip, because they are resolved by different settings.

What to do next

Send your administrator the action, not the message.

What you were trying to do, in ordinary words.
The person or the client it involved.
Roughly when you tried.

For example: I tried to reset the password for jane@example.com this morning and Avvi said I do not have permission.

Naming the action, the person and the time gives an administrator enough to find the setting. Quote the refusal as well, because the wording occasionally narrows it down.

If something doesn’t look right

If your administrator turns something on and the same refusal comes back, tell them which of the two messages you saw. A group permission does not fix a capability that is switched off for the client.

If they are confident the permission is on, ask them to check you are in the group they changed. Membership comes from your organisation’s security groups, and a recent change there takes a moment to reach Avvi.

If it persists after both checks, ask Avvi to pass the request to your IT team. Say what you were trying to do and quote the exact message.

FAQ

Q: Is this a fault?

A: No. Almost every capability starts switched off, so a refusal usually means nobody has enabled it yet.

Q: Why not name the permission?

A: The message deliberately hides internal names. Describing the action gets you a faster answer.

Q: My colleague can do this. Why can I not?

A: Capabilities are granted per user group, so two people in one organisation can genuinely have different access.

Why Avvi told me to contact my administrator covers what to say to your IT team so they can find the setting.