Access to the CMS and/or Console applications and/or the Repository Servlet
Access to applications
Opposed to versions before 14.0.0, access to applications are managed in 14.0.0 through User Roles : Every application requires a specific User Role. This page only describes which User Role is required for
- CMS application
- Console application
- Repository Servlet
After logging in into the CMS application, there are more finegrained userroles per perspective/feature in the CMS, for example the Dashboard Perspective, Content Perspective, Channel Manager Perspective etc. The userroles required for these more finegrained access are described in Userroles and not repeated here.
Access to the CMS application
Granting access to the CMS application requires the user to have userrole xm.cms.user. Any user that can authenticate and has this userrole can login into the CMS application. In general and by default, the users in the author, editor, webmaster, admin and cms-admin groups have this userrole.
Access to the Console application
Granting access to the Console application requires the user to have userrole xm.console.user. Any user that can authenticate and has this userrole can login into the Console application. By default only the default admin user and the users in the admin group (but not the cms-admin group) have this userrole.
Acces to the Repository Servlet
The Repository Servlet gives a low-level read access to the repository including query capabilities. It provides a developer tool that can be used to experiment with querying the repository. It can be accessed at the following URL (if not removed from the web.xml):
To be able to login into the Repository Servlet, a user must have the userrole xm.repository-browser.user. By default only the default admin user and the users in the admin group (but not the cms-admin group) have this userrole.