Managing App Roles
For more information about app roles, see Customizing End-User Access to Services.
App roles are associated to end-users on the one hand, and to services and other features on the other. A service or feature is visible to an end-user only if the end-user is associated with one or more of the app roles associated with the service or feature.
App roles are initially associated to end-users automatically, either by configuring a default app role or using customer roles; see Configuring End-User Authentication Types and Configuring Customer Roles.
- You configure the default app role and the association between app roles and customer roles when you manage app roles on the Select app role to change page (see below).
- You can enable/disable app roles for services and other features on this page; however, the best practice is to configure the app roles each service and feature at the same time that you configure the service or feature. For more information, see Enabling/Disabling Services in Apps.
You manage app roles on the Select app role to change page (App Settings > Enterprise Roles > App Roles). This page presents the list of app roles. For information about working with lists, see Working with Lists.
For each app role, configure:
- Profile - The profile for which this app role applies. For more information about profiles, see Customizing End-User Access to Services.
- Description - The display name of the role as it appears in other areas of the App Manager.
- Priority - Not in use.
- Default role - Assigned to any end-user. For more information, see Configuring End-User Authentication Types.
- Customer role - The customer role to which this app role is associated. For more information about customer roles, see Configuring Customer Roles.
- Menu options - The static content services to which this app role is associated. The best practice is not to manage this here, but instead when you are managing the service; see Working with Static Content and the Content Menu.
- Home page feeds - Not in use.
- RSS categories - The RSS categories to which this app role is associated. The best practice is not to manage this here, but instead when you are managing the category; see Configuring Default RSS Feeds.
- Standard RSS feeds - Not in use.
- Standard alert groups - The alert groups to which this app role is associated. The best practice is not to manage this here, but instead when you are managing the alert group category; see Configuring Alert Groups.
- Resources - Not in use.
- Maps - The maps to which this app role is associated. The best practice is not to manage this here, but instead when you are managing the map; see Adding Maps.
- Location categories - The location categories to which this app role is associated. The best practice is not to manage this here, but instead when you are managing the category; see Adding Map Location Categories.
Configuring Customer Roles
For more information about customer roles, see Customizing End-User Access to Services.
When an end-user registers using an authentication system that relies on an institution backend system, the backend system sends codes indicating the app roles to assign to the end-user. Customer roles map these codes to app roles. Ex Libris and the institution work together to configure these codes during installation. After this initial configuration, the institution can add additional codes by adding additional customer roles, as required.
You manage customer roles on the Select customer role to change page (App Settings > Enterprise Roles > Customer Roles). This page presents the list of customer roles. For information about working with lists, see Working with Lists.
For each customer role, configure:
- Name - The code the institution sends to the App Manager. For more information about this field, contact Ex Libris customer support.
- Description - The display name of the customer role as it appears in the dropdown list when configuring app roles.