Role Mappings
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.
Sample
1<?xml version="1.0" encoding="UTF-8"?>
2<!-- role-mappings-config.xml
3
4 This file maps groups to roles.
5
6 The structure of this file:
7
8 <role-mappings>
9 <groups>
10 <group name="site_admin">
11 <role>admin</role>
12 </group>
13 <group name="site_developer">
14 <role>developer</role>
15 </group>
16 <group name="site_author">
17 <role>author</role>
18 </group>
19 <group name="site_publisher">
20 <role>publisher</role>
21 </group>
22 <group name="site_reviewer">
23 <role>reviewer</role>
24 </group>
25 </groups>
26 </role-mappings>
27
28
29 Please note that by default, sites are created with the groups and roles above. However, if LDAP authentication
30 is configured, additional groups will be automatically created for the site as site members sign in via LDAP.
31 Those new groups can then be mapped to roles in this file. This then allows LDAP managed users to automatically
32 get roles within a site based on their LDAP group membership.
33
34-->
35<role-mappings>
36 <version>2</version>
37 <groups>
38 <group name="site_admin">
39 <role>admin</role>
40 </group>
41 <group name="site_developer">
42 <role>developer</role>
43 </group>
44 <group name="site_author">
45 <role>author</role>
46 </group>
47 <group name="site_publisher">
48 <role>publisher</role>
49 </group>
50 <group name="site_reviewer">
51 <role>reviewer</role>
52 </group>
53 </groups>
54</role-mappings>
Description
/role-mappings/groups/group@name
Name of the user group
/role-mappings/groups/role
Name of authoring role that group will map to
Default Site Roles
CrafterCMS comes with predefined roles out of the box for sites. Here’s a list of predefined roles for sites:
admin: Users with the
admin
role have access to site 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 workflowdeveloper: Users with the
developer
role have access to site 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 workflowreviewer: Users with the
reviewer
role 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 roleauthor
) includingRecently Published
andApproved Scheduled Items
. They do not have access to edit content.publisher: Users with the
publisher
role 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 roleauthor
) includingRecently Published
andApproved Scheduled Items
. In addition, they also have access to create, edit and submit content like theauthor
role.author: Users with the role
author
have access to create, edit and submit content
See Permission Mappings for more information on all items accessible for each role in a site.