Plato offers a rich role based security model. Roles can be used to control both the permissions a user has and the content a user can access.
Roles can be managed via the administrator dashboard from the Roles > Manage area within the navigation. From this page you can see all your roles. Below you can see the 4 default roles provided with Plato...
Each user within Plato can be associated with one or more roles. You can associate users with roles when Editing Users.
To help you get started Plato comes with four default roles. You can of course create your own roles once you need more granular control. An explanation of each default role provided with Plato is provided below.
The administrator role has similar default permissions to the staff role however the administrator role also allows access by default to the Plato administrator dashboard. Any user who belongs to the administrator role can access your Plato administrator dashboard.
The staff role by default has additional permissions within several modules. For example users who belong to the staff role can automatically create articles within Plato.Articles or docs within Plato.Docs. You should only place trusted users who will help you author content or moderate community activity into the into the Staff role. The staff role by default does not have access to the administrator dashboard.
The default member role is the role new users are placed into after they register & confirm there email address. This the main role most users will belong to.
The anonymous role is used to represent the permissions and content available to users who are not logged into Plato. if you enable roe based security within Plato and wish to ensure content is visible to users who are not logged in then you would need to associate that content with the anonymous role.