Location Management
This topic describes various location management scenarios and how they affect the display of controls in Occupation Insight. Administrators can gain an insight into the display of information in the Reports and Location Security Groups pages based on scenarios that apply.
Scenario Type | Scenario description | Location Security Group Page - Manage Security Groups configurations |
---|---|---|
Type 1 | Single location associated with a single ME-ID and an instance of Anthology Student/SIS. The location can have any number of campuses. All users can view reports and data across all campuses. | No configuration required. It's recommended institutions manage group access from ME-ID instead of this page. |
Type 2 | Single location associated with a single ME-ID and an instance of Anthology Student/SIS. The location can have any number of campuses. Each campus operates as a separate business unit and is managed centrally through a single ME-ID instance. Users are restricted to view reports and data of campuses to which they have access. |
Configurations required at a campus level.
For the value ALL assign a valid Security Group Id if users need to view reports and data across campuses to which access is enabled. Otherwise, retain the default value. |
Type 3 | Multiple locations are all associated with a single ME-ID with each location associated with a unique Anthology Student/SIS instance. Each location can have any number of campuses. Users are restricted to view reports and data across all campuses in the location to which they have access. |
Configurations required at the location level.
For the value ALL assign a valid Security Group Id if users need to view reports and data across campuses to which access is enabled. Otherwise, retain the default value. |
Type 4 | Multiple locations are all associated with a single ME-ID with each location associated with a unique Anthology Student/SIS instance. Each location can have any number of campuses. Users are restricted to view reports and data of the location and the campuses they have access to. |
Configurations required at the campus level in each location.
For the value ALL assign a valid Security Group Id if users need to view reports and data across campuses to which access is enabled. Otherwise, retain the default value. |
The following table describes guidelines to ensure optimal implementation of the above tenant management scenarios:
Guideline | Outcome if not followed |
---|---|
For the Occupation Insight enterprise application, location and campus access using security groups and roles configured in Occupation Insight will override the roles assigned to the security groups defined in ME-ID. | If the location and campuses are not configured with a security group in Occupation Insight, the Security Groups and the assigned Role as defined in ME-ID prevails. |
If a location is configured with a security group, it's required that all other locations must also be configured with a security group to allow access to them, i.e., access to all campuses. | Users will only be able to login to the location/campus associated with the user's security group. |
If a campus in a location is configured with a security group, all other campuses in the location must also configured with a security group to allow access to those campuses. | Users will only be able to login to the location/campus associated with the user's security group. |
In a multi-location and multi-campus scenario, if a campus in a location (say X) is configured with a security group:
|
Users will only be able to login to the location/campus associated with the user's security group. |
The following table lists operations that users can perform on the Home and Reports pages based on roles granted to them:
Page | Operation | Scenario (Security configuration) type |
Role |
||
---|---|---|---|---|---|
Administrator | Contributor | Reader | |||
Home Page | Manage Security Groups menu option is enabled (Access to the Location Security Groups page) | All Types | Yes | No | No |
Select Location dropdown
The text Type 1 - Type 4 in the next column refers to scenarios described for each type in the first table above. |
Type 1 | No | No | No | |
Type 2 | No | No | No | ||
Type 3 | Yes | Yes, if the user has access to more than one location. | Yes, if the user has access to more than one location | ||
Type 4 | Yes | Yes, if the user has access to more than one location. | Yes, if the user has access to more than one location | ||
Select Campus dropdown
The text Type 1 - Type 4 in the next column refers to scenarios described for each type in the first table above. |
Type 1 | No | No | No | |
Type 2 | Yes | Yes, if the user has access to more than one campus. | Yes, if the user has access to more than one campus. | ||
Type 3 | Yes | The dropdown will be visible or disabled depending on the user's access to locations and campuses. | The dropdown will be visible or disabled depending on the user's access to locations and campuses. | ||
Type 4 | Yes | The dropdown will be visible or disabled depending on the user's access to locations and campuses. | The dropdown will be visible or disabled depending on the user's access to locations and campuses. | ||
Reports Page | Edit Report | Yes | Yes | No | |
Embed Report | Yes | No | No | ||
Publish Report | Yes | Yes | No |
Note: Information displayed in reports that are shared with the ALL option will depend on the campuses a user selects. For example, if the user selects Campus1 even though access is enabled for ALL campuses, information in the report will display only for Campus1.