Docs Navigation Open
Permissions
Use roles for actions and groups for scope: that is the practical permission model in the manager.
Permissions in Evolution CMS are easiest to understand when you separate actions from content scope.
Actions
Roles control what a manager user may do: edit resources, manage elements, install packages, change settings, manage users, and so on.
Scope
Document groups and related user-group mapping control which parts of the resource tree a manager can access.
Practical Pattern
- give editors only the actions they need
- restrict whole tree branches with document groups when teams work on different areas
- reserve admin rights for a very small set of trusted users
Related Models
EvolutionCMS\\Models\\UserEvolutionCMS\\Models\\UserRoleEvolutionCMS\\Models\\UserRoleVar
See also Roles and Permissions.
Previous
Configuration Reference
Review the main configuration surfaces used by Evolution CMS: system settings, runtime environment, URLs, cache behavior, and package-level config.
Next
CLI
Use the evo installer, Artisan commands, and Composer together in a predictable way in Evo 3 projects.