...
Like this, you can add as many Security Groups as you would like to any attribute(s).
How
...
do you assign
...
a Security Group to a
...
user?
The Security Group access for a User user is set up in Manage Users/Contacts. As an example, let us create a security group for Location attributea Company.
|
Enter the security group description, select the Attribute ID and save.
|
The new security group shows for Location as given below.
|
Let us assign this newly created security group to a user. Navigate to Manage Users/Contacts and access the user page.
|
Create a new user/contact or edit an existing user. For more details on adding a new user, please click here.
In this case, the existing user account is edited to change the Row level security for Location.
...
In Row Level security, select On the Invite/Edit User page, configure the Row Level security to the newly created security group for Location attribute and save the changes. This will restrict limit the user to access the candidates' 's access to candidate data specific to that location in consoles.
...
The console data for the above user displays only the 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" 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" link.
...
Check the Information tab for Location. The new Location security group shows in the information.
...
The above restriction on user access is also applicable to Elasticsearch as well as dashboards.
If the user tries to access the candidate data that does not belong to the Location the user has access to, then the system 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, the user will be redirected to the following unauthorized access page.
...
Elasticsearch:
In Elasticsearch, all the category related search results and their actions oblige row level security.
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.
Examples:
...
...
Select any candidate and click on the invitation ID link. The page redirects to error message if the user has no access to the candidate data.
...
When clicked on related action for the above invitation, the page displays error message.
...
...
company within consoles and dashboards.
|
