Most WHMCS installs start with one staff account: the owner's, with every permission switched on. Then a support hire gets the same login "just for now", a freelancer keeps the account they used to fix a module, and a billing assistant leaves without anyone switching them off. A year later five people can do anything, and the Admin Log can't tell you who did what.
The good news is that WHMCS already has the tools to fix this:
- Administrator roles. WHMCS ships with Full, Sales and Support Only, and you can add custom roles such as Billing or Module debug. Keep Full to one or two people.
- Read the permission types. List and View are low risk. Delete and Configure are the dangerous ones, and some Create permissions quietly need Manage too.
- Invite, don't hand out passwords. Send Invite Link lets new staff pick their own credentials, so no password travels through chat.
- Offboard properly. Disable old accounts and move API credentials off personal admins before someone leaves.
Roles still can't stop someone who has a valid password, which is where a second login factor comes in.
The full guide has a sample role plan for a small hosting team, the permissions worth singling out and an offboarding checklist. Read our guide to WHMCS admin roles, least privilege and offboarding on the ShoHost blog.
