...
Role Customization: Users can be assigned roles with specific permissions based on their responsibilities and requirements.
Permission Specifications:
...
Web Manager - The main web manager permission.
CMS Settings
Custom results Panel
Flows
Forms
Front End Editing
Locales
Maxxton Services (Connectivity).
Menus
Pages
Posts
Site Map Settings - (site.settings.sitemap).
Site
Site Settings - (site.settings.general).
Templates
Theme Settings
Translations
Webcontents
Free Search
Conditional sets
Categories
Dynamic Sitemaps
Data Layers
Imitate user
Image Manager
Granular Control: For each section, administrators can specify actions like READ, EDIT, CREATE, DELETE, and EXECUTE (all) for specific users.
Accessing Web Manager:
If a user encounters a popup indicating restricted access or doesn't see specific sections in the Web manager, it's likely due to their assigned role's permissions. In such cases, administrators should configure the correct role for the user in the Backoffice Manager.
...
Default set of permissions:
Whenever we create a new client, we always create an a Maxxton Admin permission group and assign all permissions to it. This ensures that we consistently have the default set of roles within the back office manager.
For more understanding you can refer the install scripts
1. Source of install_permission_concern_data.sql - newyse - Bitbucket Maxxton this permission script runs only per schema and Source of install_permission_data.sql - newyse - Bitbucket Maxxton this one for each concern and permission groups are per concern.
...