Understand roles

You can filter content based on an assigned role within the system. For example, large institutions with big menus and a large number of users may have more content to navigate. Using roles allows you to limit the content that different types of users see.

You can use roles to do the following:
  • Target specific content to specific people.
  • Make content available to different audiences, such as students, prospective students, faculty, and alumni.
There are two ways to target content by roles:
  • Role Service Roles. These are defined within the Role Service you specify within the General Settings. They are groupings of people defined within your SIS or LDAP.
  • Mobile Roles. These are roles you define within the Cloud Configuration tool. This allows you to group Role Service roles together or use different names from the ones that are defined in your Role Service.
For example, a Role Service Role may include freshmen, sophomores, juniors, and seniors. In Ellucian Mobile, you may want to target content to all students. You can create a Mobile Role called “All Students” and map all four student groups to it. Mobile roles are set up within the Roles tab in the General Settings. You can apply Role Service roles or Mobile roles to specific application modules within each application module configuration screen. You can apply Mobile roles to any application module type (with an exception of the Header type) using the “Available to” field.
  • The default in a new module is that everyone can see the role; whether logged in or not.
  • Use of Mobile Roles is dependent on the Role Service defined in the General Settings.
  • Roles are not applied to Header modules. A header is visible based on the settings of the modules beneath it.
Note: Mobile users must be signed in to have a role assigned to them. If you add role filtering to a module, users must sign in before they can view the content of that module.

Complete the Roles tab for your configuration.