Journey Manager (JM) The transaction engine for the platform. | System Manager / DevOps | All versions This feature is related to all versions.
Manager comes with a number of permissions to control user access to restricted content, such as form spaces and modules. Permissions are specific to each module and a form space, which of them has the standard set of pre-defined permissions. However, you can define your own permissions and implement security rules.
Permissions are mapped to standard roles which are in turn related to certain product features. By assigning roles to users, they are granted the necessary permissions to use the associated features. This is known as role-based access control.
A set of permissions is associated with each role. Assigning several roles to a user grants that user all the permissions associated with all the assigned roles. Take care to review the complete set of permissions granted to a user to ensure they don't have any permissions they shouldn't have.
The Manager Home Dashboard has the following permissions that govern user access:
By granting the Edit and Remove permissions, it doesn't automatically grant the View permission. For each of Edit and Remove permissions, you need to include the View permission to the role. For example, to allow users to create new or modify existing organizations in Manager, their role must require the Organization View and Organization Edit permissions.
Manager has different sets of permissions for the following modules:
Next, learn about standard roles.