Users only sees the items that they have been granted access to based on the permissions granted to the Role they have been assigned to. The role mappings configuration file defines the mapping between the group that the user belongs to and the studio authoring role. To modify the role mappings, click on from the bottom of the Sidebar, then click on Configuration and select Role Mappings from the dropdown list.
Here’s a sample Role Mappings Configuration file (click on the triangle on the left to expand/collapse):
1<?xml version="1.0" encoding="UTF-8"?> 2<!-- 3 ~ Copyright (C) 2007-2022 Crafter Software Corporation. All Rights Reserved. 4 ~ 5 ~ This program is free software: you can redistribute it and/or modify 6 ~ it under the terms of the GNU General Public License version 3 as published by 7 ~ the Free Software Foundation. 8 ~ 9 ~ This program is distributed in the hope that it will be useful, 10 ~ but WITHOUT ANY WARRANTY; without even the implied warranty of 11 ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 12 ~ GNU General Public License for more details. 13 ~ 14 ~ You should have received a copy of the GNU General Public License 15 ~ along with this program. If not, see <http://www.gnu.org/licenses/>. 16 --> 17 18<role-mappings> 19 <groups> 20 <group name="site_admin"> 21 <role>admin</role> 22 </group> 23 <group name="site_developer"> 24 <role>developer</role> 25 </group> 26 <group name="site_author"> 27 <role>author</role> 28 </group> 29 <group name="site_publisher"> 30 <role>publisher</role> 31 </group> 32 <group name="site_reviewer"> 33 <role>reviewer</role> 34 </group> 35 </groups> 36</role-mappings>
Name of the user group
Name of authoring role that group will map to
Default Project Roles
CrafterCMS comes with predefined roles out of the box for projects. Here’s a list of predefined roles for projects:
admin: Users with the
adminrole have access to project configuration files, creating/editing layouts, templates, taxonomies, content types, scripts, etc. in addition to creating and editing content, as well as the ability to approve and reject workflow
developer: Users with the
developerrole have access to project configuration files, creating/editing layouts, templates, taxonomies, content types, scripts, etc. in addition to creating and editing content, as well as the ability to approve and reject workflow
reviewer: Users with the
reviewerrole have the ability to approve and reject workflow. They also have access to a number of dashboards which are not available to content contributors (users with role
Approved Scheduled Items. They do not have access to edit content.
publisher: Users with the
publisherrole have the ability to approve and reject workflow. They also have access to a number of dashboards which are not available to content contributors (users with role
Approved Scheduled Items. In addition, they also have access to create, edit and submit content like the
author: Users with the role
authorhave access to create, edit and submit content
See Permission Mappings for more information on all items accessible for each role in a project.