WHMCS Addon Not Showing in the Admin Menu? Fix Access Control

You install an addon module in WHMCS, activate it, and it works fine for you. Then a staff member logs in and the module is nowhere to be found. It is not in the Addons menu, and if you send them the direct URL they get an access-denied error.

Nothing is broken. The addon is not buggy. WHMCS is doing exactly what it was configured to do: hiding the module from admins who have not been granted access to it.

It comes up constantly in WHMCS support, and the fix takes about a minute once you know where to look. It applies to every addon module, whether you built it, bought it, or downloaded it for free.

The symptom: activated but invisible to some admins

The pattern looks like this:

• The addon is activated. You can see it in the Addons menu and open its configuration.
• A different staff member cannot see it at all, or sees it but cannot open it.
• The module's own License Status shows Active, so licensing is not the problem.

If that matches what you are seeing, the cause is almost never the addon itself. It is WHMCS access control.

Why it happens: WHMCS Access Control, not the addon

Every addon module in WHMCS gets an Access Control block automatically. WHMCS renders it for you. The addon developer does not write it and cannot bypass it. It looks like this on the module's configuration row:

Choose the admin role groups to permit access to this module: [ ] Full Administrator [ ] Sales Operator [ ] Support Operator

Only the role groups you tick can see and open the module. A Full Administrator usually has it ticked from the start, which is why the owner account works. Any other role, like Sales Operator or a custom role, stays locked out until you add it.

So the admin who cannot see the module is not hitting a bug. They belong to a role group that has not been granted access yet.

The fix: two requirements

Granting access is two settings, not one. Both have to be true, or the module stays hidden.

Requirement 1: the role needs the Addon Modules permission

Where: Configuration > System Settings > Administrator Roles (older versions: Setup > Staff Management > Administrator Roles)

Open the role your staff member belongs to and make sure the Addon Modules permission is enabled. Without this permission, the role cannot access any addon, no matter what the per-module setting says.

Requirement 2: tick the role group in the addon's Access Control

Where: Configuration > System Settings > Addon Modules (older versions: Setup > Addon Modules)

Find the addon, open its row, and in the Access Control section tick the role group your staff member belongs to. Then click Save Changes.

That is the setting most people miss. The permission in Requirement 1 unlocks addons in general. The tick here unlocks this specific addon for this specific role.

Verify: log in as that staff member

Do not assume it worked. Confirm it.

1. Have the staff member refresh or log out and back in.
2. Open the Addons menu. The module should now be listed.
3. Open the module and walk through its tabs.

If they can reach it and use it, you are done. This is a settings change, not a reinstall or a code fix.

Still cannot see it? Quick checklist

If the module is still hidden after saving, work through these in order:

Check	What to confirm
Right role	The staff account belongs to the role you actually ticked, not a similarly named one
Both settings saved	The Addon Modules permission is on AND the role group is ticked in Access Control
Session refreshed	The staff member logged out and back in after you saved
Module activated	The addon shows Deactivate (meaning it is active), not Activate
License active	The module's own License Status reads Active, not Invalid

If access is granted but a specific tab or button errors only for the limited role, that is a different problem. It means the addon needs a WHMCS permission that the restricted role does not have. Note which action fails and which role, then raise it with the addon vendor.

This applies to every addon

Access Control is native WHMCS behavior, so the exact same two steps apply to any module you run. If you use the MX Modules addons, granting a staff member access to MX Metrics, the MCP Server, or MX Proposals is the same flow: enable the Addon Modules permission on their role, then tick that role in each module's Access Control.

Setup details for each are in their docs: MX Metrics, MCP Server, and MX Proposals.

A good habit while you are in there: give each staff member the least access they need. A support agent rarely needs your billing analytics module, and a sales operator rarely needs your server automation tools. Access Control is where you enforce that.

Frequently Asked Questions

Why can I see the addon but my staff cannot?

Your account is almost certainly a Full Administrator, which is ticked in the module's Access Control by default. Your staff member belongs to a different role that has not been ticked yet. Add their role in Configuration > System Settings > Addon Modules, open the module, tick their role group, and save.

Is this a bug in the addon?

No. Access Control is generated by WHMCS for every addon module. The developer of the addon does not control it. If a module is activated and licensed but invisible to some admins, it is an access setting, not the code.

What is the difference between the role permission and Access Control?

The Addon Modules permission on the role decides whether that role can use addons at all. The Access Control tick on each module decides which of those roles can use that particular module. You need both: the general permission and the per-module tick.

Do I need to reactivate the module after changing Access Control?

No. Access Control changes take effect as soon as you save. The staff member only needs to refresh or log back in to see the module appear in the Addons menu.

The admin has access but a tab throws an error. What now?

That is a separate issue from visibility. It usually means the restricted role is missing another WHMCS permission that the module relies on for that action. Note the exact tab or button and the role, compare it against a Full Administrator, and report it to the addon vendor with those details.

Related

• 10 WHMCS Admin Settings Most Providers Miss - The settings that quietly cost you money and support tickets
• What Changed in WHMCS 9 for Hosting Providers - Admin and configuration changes worth knowing
• MX Metrics - Revenue analytics you can scope to the right staff with Access Control