...
The Security Group access for a User is set up in Manage Users/Contacts. As an example, let us create a security group for Location attribute.
...
The console data for the above user displays only the candidates rows belonging to that Location security group. Let us check this in the Invitation Console.
With the user login, navigate to invitation console and click on "Search invitation console " button. This displays the invitation data that the user has access to.
Now let us check the location information for any invitation. Select an invitation and click "Info and Actions" for any invitationlink.
|
Check the Information tab for Location. The newly set up new Location security group shows in the information.
...
If the user tries to access the candidate data that does not belong to the Location the user has access to, then the user will be redirected to the unauthorized access pagesystem displays an unauthorized error message.
Dashboards example:
Click on the number or segment of the graph in the I-9 Insight chart.
...
The user can see the list of all I-9 IDs of the segment as shown below, but the drill down data can be seen only for the candidates that belong to the locations the user has access to.
|
|
The user cannot access the candidate data that belong to locations not configured for him. When clicked on those I-9 IDs other than , the location the user has access to, then they will be redirected to the following unauthorized access page.
...
In Elasticsearch, all the category related search results and their actions oblige row level security except I-9 Status, I-9 Compliance and I-9 Life Cycle.
In However, in I-9 Status, I-9 Compliance and I-9 Life Cycle categories, the search results show all the rows but the drill down redirects the user to the unauthorized access page if the candidate does not belong to the locations the user has access to.
...