Skip to main content
Navigation Path: Admin Dashboard → Settings → User Roles & Permissions
URL: /admin/PermissionOption

Overview

Create custom user roles and configure granular access permissions to control what different users can see and do on your platform.

Roles

Create and manage roles

Permissions

Granular access control

Access Levels

Define role capabilities

Security

Protect sensitive areas

User Roles

Define different user types with specific permissions and access levels.

Default Roles

RoleTypical UseAccess Level
AdministratorPlatform ownersComplete control
ManagerTeam leadsMost features
SupportCustomer serviceCustomer-facing features
UserRegular customersBasic features only
GuestTrial usersMinimal access

Creating Custom Roles

  1. Click “Add Role” button in the User Roles section
  2. Choose a descriptive name for the role (e.g., “Sales Team”, “Technical Support”)
  3. Configure feature access by selecting appropriate permissions
  4. Review all permissions to ensure they match the role’s responsibilities
  5. Save the role to make it available for assignment to users
Role Design: Create roles based on job functions and follow the principle of least privilege. Grant only the minimum permissions necessary for users to perform their duties effectively.
Security: Be cautious when granting administrative permissions. Too many administrators can create security risks and make it difficult to track changes. Limit admin access to trusted team members only.

Permission Categories

Configure granular access control across different areas of your platform.

Dashboard & Overview

  • Full Access, Limited Access, or No Access to dashboard widgets

User Management

PermissionDescription
View UsersSee list of all users
Create UsersAdd new accounts
Edit UsersModify user information
Delete UsersRemove accounts
Assign RolesChange user roles

Website Management

PermissionDescription
View WebsitesSee all websites
Create WebsitesCreate new websites
Edit WebsitesModify settings
Delete WebsitesRemove websites
Suspend WebsitesDisable websites
Access Control PanelDirectAdmin access

Domain Management

PermissionDescription
View DomainsSee all domains
Register DomainsRegister new domains
Manage DNSEdit DNS records
Transfer DomainsInitiate transfers
Renew DomainsProcess renewals

Billing & Payments

PermissionDescription
View InvoicesSee all invoices
Create InvoicesGenerate invoices
Process PaymentsAccept payments
Issue RefundsProcess refunds
View ReportsFinancial reports
Manage PricingEdit pricing

Settings & Configuration

PermissionDescription
General SettingsModify platform settings
Payment GatewayConfigure payments
Email SettingsManage email config
API SettingsAccess API credentials
Security SettingsModify security

Support & Tickets

PermissionDescription
View TicketsSee all tickets
Create TicketsOpen tickets
Reply to TicketsRespond to customers
Close TicketsMark resolved
Assign TicketsAssign to team
Delete TicketsRemove tickets
Permission Levels: Each permission can be set to Full Access (complete control), Read-Only (view only), Limited (specific actions), or No Access (feature hidden).

Common Role Configurations

  • Customer Service
  • Sales Team
  • Technical Support
  • Finance
  • Dashboard: Limited (customer metrics)
  • View Users: Read-only
  • Edit Users: Limited (contact info only)
  • View Websites: Read-only
  • Suspend Websites: Yes
  • Tickets: Full access
  • Invoices: Read-only
  • Settings: No access

Best Practices

  • Grant minimum necessary access for each role
  • Start with minimal permissions and add as needed
  • Review permissions regularly (quarterly recommended)
  • Remove unnecessary permissions promptly
  • Document why each permission is granted
  • Require justification for permission increases
  • Audit permission usage to identify unused access
  • Separate conflicting responsibilities (e.g., finance and technical)
  • Require multiple approvals for sensitive actions
  • Don’t combine financial and technical full access in one role
  • Create specialized roles for specific functions
  • Avoid creating “super users” with all permissions
  • Use role hierarchy to organize permissions logically
  • Document role responsibilities clearly
  • Limit payment settings access to finance team only
  • Restrict API credentials to technical administrators
  • Control data deletion permissions carefully
  • Monitor admin actions with logging
  • Require strong passwords for all admin accounts
  • Enable two-factor authentication for sensitive roles
  • Set up alerts for critical permission changes
  • Assign appropriate role immediately upon account creation
  • Revoke all access when employee leaves organization
  • Transfer ownership of work before removing access
  • Change shared passwords after employee departure
  • Review and update roles when job responsibilities change
  • Maintain list of who has what access
  • Conduct regular access reviews

Troubleshooting

Issue: User receives “access denied” or feature is hiddenSolutions:
  1. Verify user’s assigned role in user management
  2. Check role permissions for the specific feature
  3. Grant necessary permissions to the role
  4. Clear application cache
  5. Have user log out and log back in
  6. Test with different user account to isolate issue
Issue: Permission changes don’t take effectSolutions:
  1. Save permission changes again
  2. User must log out and back in for changes to apply
  3. Clear application and session cache
  4. Test in incognito/private browsing mode
  5. Verify no conflicting permissions exist
  6. Check for permission inheritance issues
Issue: Too many users have admin accessSolutions:
  1. Audit all users with admin role
  2. Create appropriate custom roles for specific needs
  3. Downgrade unnecessary administrators to custom roles
  4. Implement regular permission reviews
  5. Document who needs admin access and why
  6. Set up approval process for admin access
Issue: Role configuration changes don’t persistSolutions:
  1. Check for validation errors on save
  2. Verify you have permission to modify roles
  3. Clear browser cache and try again
  4. Check server logs for errors
  5. Ensure database connection is stable
  6. Try creating role with different name

Quick Reference

Permission Checklist

Creating a Role:
  • Choose clear, descriptive name
  • Define job function and responsibilities
  • Set minimum necessary permissions
  • Test with dummy account before deployment
  • Document role purpose and permissions
  • Get approval from management
Regular Maintenance:
  • Quarterly permission audits
  • Remove inactive users promptly
  • Update roles for job changes
  • Review admin access regularly
  • Update role documentation
  • Monitor permission usage

Common Permission Combinations

NeedPermissions
View customer infoView Users (read-only)
Create accountsView + Create Users
Manage supportView/Reply/Close Tickets
Process ordersView Users + Create Invoices + Process Payments
Technical supportView/Edit Websites + Manage DNS + View Tickets