Admin User Roles

Adding / Editing User Roles

There is no limit to the number of roles you can create and you can add or remove admin users from roles at any time. See ‘Admin Users’ for details on assigning roles.

To create a new role click the 'ADD ADMIN ROLE' button at the top of the page, or to edit an existing role click on the role’s name or the associated pencil icon on the far right.
The trash can icon allows you to delete a role.

User permissions cover almost all areas of the admin, as well as FTP access, with most items allowing individual control for viewing, creating, editing and deleting items.

There are also permissions for allowing access to module and system settings, reports and even controlling admin users and roles.

Use the checkboxes to enable or disable group level permissions, or sub-level permissions (using the arrow to expand a group), and click the ‘SAVE’ button at the bottom to save the permissions for that role.

For Custom Modules there is a permissions group called “Default Custom Module Permissions” which will be applied to any new Custom Modules that are created. However, each Custom Module will also have its own set of permissions available for independent control if needed.

For sites on the ESSENTIAL plan, where custom admin user roles are not available, all permissions, including FTP access, will be active for any admin user added.

Use Cases

Admin User Roles are suited for securely controlling access to sections of the admin interface as well as the tasks that the admin user can perform within those sections.

This makes it ideal for providing admin access to a variety of different people for different job roles without risking exposure of sensitive information or site misconfigurations by untrained/unauthorised users.

For example; you or your client might employ the services of a third party SEO provider and need to provide site content control to them. However, access to the CRM needs to be prohibited from third parties - or perhaps they can 'view' CRM records but not 'edit' them. Admin User Roles can be configured to do this.

Another use case might be to restrict access to your client for certain features, either while in development or due to how your agency bills for services and site functionality - independent to the actual WebinOne site plan. Eg: While the site may require the eCommerce plan for various functionality, a shopping cart is not part of your project agreement with your client and would otherwise require additional fees/contracts in order to be implemented under the terms of your agency.

For controlling the appearance or layout of the admin menu and what the content managers most need to see, it is usually best to use the ‘Admin Menu Configurator’ rather than permissions set via Admin User Roles.