Contributors:
Admin User Roles
Admin User Roles let you control exactly what each admin user can see and do across every section of your WebinOne site admin.
You can find Admin User Roles under 'Settings' > 'Admin User Roles'. From here you can create as many roles as you need, each with its own permission set, and assign them to individual admin users.
The permissions interface organises access into a three-tier hierarchy - Section, Module, and Actions - making it straightforward to manage permissions in larger projects with many modules. Each module's top-level checkbox reflects the combined state of its child permissions at a glance, and search and filter tools help you locate specific permissions without scrolling through the full list.
Adding and Editing User Roles
There is no limit to the number of roles you can create. To add a new role, click "ADD ADMIN ROLE" at the top of the list. To edit an existing role, click the role name or the edit icon () on the right. To delete a role, use the delete icon ().
See 'Admin Users' for details on assigning roles to individual admin users.
Settings
The display name for this role. eg: "Content Editor" or "SEO Manager".
Permissions
The Permissions panel lists all available admin modules, grouped by Section. Each module row shows a checkbox indicating the current permission state for that module, and an edit icon () to open and configure the individual action-level permissions within it.
To enable or disable all permissions across the entire role at once, use the Enable All button at the top right of the Permissions panel.
Permission states
Each top-level module checkbox reflects the combined state of its child action permissions. Three states are possible:
All action permissions for this module are enabled.
All action permissions for this module are disabled.
Some, but not all, action permissions within this module are enabled. This provides a quick visual indicator that partial access has been configured for this module.
Permission hierarchy
Permissions follow a three-tier structure that mirrors the layout of the admin interface:
- Section - the top-level grouping corresponding to major areas of the admin, such as 'Content', 'CRM', 'Extensions', etc.
- Module - an individual feature or area within a section, such as 'Pages', 'Forms', or 'Blogs'. Each module appears as a row with its own checkbox and edit icon.
- Actions - the specific operations available within a module, such as Can View, Can Add, Can Edit, Can Delete, and Can Bulk Delete. Click the edit icon () on the module row to configure action-level permissions.
For Custom Modules, a Default Custom Module entry controls the permissions that will be applied to any new Custom Modules created in future. Each existing Custom Module also has its own independent permissions entry for more granular control.
Search and filtering
Use the search and filter controls at the top of the Permissions panel to quickly locate specific modules, particularly useful when a site has a large number of Custom Modules.
Type any part of a module name to filter the permissions list in real time.
Filter the list by current permission state:
- All - show all modules regardless of their current state
- Enabled - show only modules with at least one permission enabled
- Disabled - show only modules with all permissions disabled
Narrow the list to a specific functional area of the admin. Available sections include 'Monitoring & Analytics', 'Content', 'CRM', 'Email Notifications', 'Email Marketing', and others depending on your site's active features and installed extensions.
Click "SAVE" at the bottom of the page to save your permission changes for the role.
Use Cases
Admin User Roles are well suited to securely controlling access to sections of the admin interface, as well as the specific tasks that admin users can perform within those sections.
This makes them ideal for providing admin access to a variety of people with different job roles, without risking exposure of sensitive information or unintended site changes by untrained or unauthorised users.
For example, you or your client might need to provide site content access to a third-party SEO provider - but that provider should not be able to view or edit CRM records. Admin User Roles can be configured precisely for this, with CRM permissions disabled entirely while full Content access is enabled.
Another use case is to restrict client access to certain features during development, or in line with your agency's service agreement. For instance, even if the site requires the eCommerce plan for other functionality, you can prevent client access to the shopping cart section until it is within the agreed project scope.
For controlling the visibility and layout of the admin menu rather than functional access, use the 'Admin Menu Configurator' instead. Admin User Roles control what users can do - the Menu Configurator controls what they can see in the navigation.
On the ESSENTIAL plan, custom admin user roles are not available. All permissions, including FTP access, will be active for any admin user added on this plan.