Access to the CMS, Console Applications, and Repository Servlet
Overview
Starting with version 14.0.0, Bloomreach Content manages access to applications using User Roles. Each application requires a specific user role for access. This page outlines the required user roles for:
- CMS application
- Console application
- Repository Servlet
For permissions within the CMS application—such as access to the Dashboard Perspective, Content Perspective, or Channel Manager Perspective—refer to the User Roles documentation for detailed requirements. This page does not cover those finer-grained roles.
CMS Application Access
To access the CMS application, a user must have the xm.cms.user user role. Any authenticated user with this role can sign in to the CMS application.
By default, the following groups have the xm.cms.user role:
- author
- editor
- webmaster
- admin
- cms-admin
Console Application Access
To access the Console application, a user must have the xm.console.user user role. Any authenticated user with this role can sign in to the Console application.
By default, only the following have the xm.console.user role:
- The default
adminuser - Users in the
admingroup
Note: Users in the cms-admin group do not have this role by default.
Repository Servlet Access
The Repository Servlet provides low-level read access to the repository, including query capabilities. This tool is intended for developers to experiment with repository queries. The servlet is available at:
http://host:port/cms/repository
Access to the Repository Servlet requires the xm.repository-browser.user user role. By default, only the following have this role:
- The default
adminuser - Users in the
admingroup
Users in the cms-admin group do not have this role by default.
If the Repository Servlet is not available, verify that it has not been removed from the web.xml configuration.