Manage end users, cloud users and admin ACLs in Virtualizor

Virtualizor separates who can do what: normal users manage VPS you create for them, cloud users get a pool of resources and create their own VPS (useful for resellers and teams), and admin users with ACLs help you run the platform. Setting these up carefully keeps customers in their lane and staff limited to their tasks.

Before you start

• Virtualizor admin access with plans and IP pools ready; see plans and VPS.

Normal users

1. Go to Users → Add User.
2. Enter email and password and choose type Normal User.
3. Save, then assign VPS to the user when creating them.

Normal users can manage only their assigned VPS in the end-user panel (power, VNC, reinstall, rDNS and the other features you enable).

Cloud users

1. Go to Users → Add User and choose Cloud User.
2. Set the resource pool: maximum number of VPS, total RAM, disk, CPU cores, bandwidth and IPv4/IPv6 addresses.
3. Choose which servers or server groups and which OS templates they may use.
4. Save. The cloud user can now create, resize and delete VPS within the pool from the end-user panel.

Cloud users suit resellers who sell VPS themselves, agencies managing many client servers, or internal teams. Limit the pool to what their contract covers.

Restrict end-user features

Under Configuration → End User Panel (or Master Settings), disable features you do not offer – for example custom ISOs, OS reinstall frequency, hostname changes or the API. Plans can also enable or disable rescue mode, VNC and backups per VPS.

Admin users and ACLs

1. Go to Users → Admin ACL → Add ACL.
2. Name the role, for example Support Staff, and tick only the permissions it needs: list VPS, start/stop, VNC, view logs – but not delete VPS, edit plans or change configuration.
3. Create the staff account under Users → Add User with type Admin and select the ACL.

Require two-factor authentication for all admins under the admin security settings, and review admin logs regularly. See also account security.

Suspend and delete users

• Suspend a user to block panel login; suspend their VPS separately if service should stop.
• Delete a user only after their VPS are deleted or moved to another user.
• With WHMCS, suspension and termination happen automatically based on invoices; see WHMCS Virtualizor module.

Troubleshooting

• Cloud user cannot create VPS: pool exhausted, no allowed server, or no free IPs in the pools they can use.
• Staff sees too much: tighten the ACL; changes apply at next login.
• User sees a VPS they should not: check VPS ownership under List VPS.

Next steps

• Backup plans.
• Updates and maintenance.
• The end-user panel.