In previous versions of EmpowerID, users could not see any resources within their respective organizations without an RBAC assignment to those resources. For example, a user could not look up any information about the users within their office until they were granted the Viewer Access Level for each of those users. This is no longer the case as RBAC control over the visibility of resources has been replaced by three types of policies, Visibility Restriction policies, Column Visibility Filter policies and Data Visibility Filter policies. Visibility Restriction policies most resemble RBAC and can be implemented with ease. Column Visibility Filters and Data Visibility Filters are SQL-based filters that you write against the EmpowerID Identity Warehouse to show and hide data at the column and attribute level. Each of these policy types are discussed in greater detail below. (Column Visibility Filter policies and Data Visibility Filter policies are discussed under the Visibility Filter Policies heading.)
Visibility Restriction policies are policies that you can create to limit the ability of people to view resources in EmpowerID. These policies are similar to RBAC delegations in that you can assign them to any EmpowerID Actor, such as a Management Role, group, Query-Based Collection (SetGroup), and so forth. Once the policy has been assigned to an actor, any person belonging to that actor (such as being in a Management Role with the policy) receives the policy. For example, if your organization uses the services of contractors, you could create a Visibility Restriction policy that allows contractors to see only other contractors within the organization, and apply that policy to a group or Management Role designated for Contractors. Then, when a contractor who belongs to that group or role logs in, that contractor will only be able to see other contractors.
Visibility Filter policies are SQL statements written against the EmpowerID Identity Warehouse that give you power and flexibility in determining which users can view what objects—even allowing you to specify the visibility of individual attributes—without needing to be concerned with the complexities of location-based delegations. Visibility Filter policies can be assigned to any EmpowerID Actor type, such as a Management Role, Business Role and Location, group, or Set Group as well as to individual accounts and people.
Visibility Filter Policies come in two types, the Column Visibility Filter policy and the Data Visibility Filter policy.
The following code snippet shows the how the substitution for the Email is written in the filter.
'N/A' AS Email, [TABLEALIAS].*
EmpowerID includes the following Column Filter Policies that you can use out of the box:
Column Filter Policy | EmpowerID Component | Purpose | Assignee Type |
---|---|---|---|
Sample AccountView removing visibility on email | Account | Substitutes the actual value of the Email attribute on an account with "N/A" for anyone assigned the filter. | Empty |
EmpowerID includes the following Data Filter Policies that you can use out of the box:
Data Filter Policy | EmpowerID Component | Purpose | Assignee Type |
---|---|---|---|
Anonymous user cannot see anyone | Person | Anonymous users cannot see anyone in EmpowerID | Person |
Sample filter for Account (see only accounts in or below my locations) | Account | Filters the accounts that can be viewed in EmpowerID to include only those in the assignee's location or below | Empty |
Sample filter for Account (see only own accounts) | Account | Assignees cannot view any accounts in EmpowerID beyond their own | Empty |
Sample filter for Business Roles (see only business roles in a list) | OrgRole | Filters the business roles that can be viewed in EmpowerID to include only those specified | Empty |
Sample filter for Computer (see only computers in or below my locations) | Computer | Filters the computers that can be viewed in EmpowerID to include only those in the assignee's location or below | Empty |
Sample filter for Groups (see only groups in a list) | Group | Filters the groups that can be viewed in EmpowerID to include only those specified | Empty |
Sample filter for Groups (see only groups in a specific OU) | Group | Filters the groups that can be viewed in EmpowerID to include only those in a specified OU | Empty |
Sample filter for Groups (see only groups in or below my locations) | Group | Filters the groups that can be viewed in EmpowerID to include only those in the assignee's location or below | Empty |
Sample filter for Groups (see only groups I belong to) | Group | Filters the groups that can be viewed in EmpowerID to include only those to which the assignee belongs | Empty |
Sample filter for Locations (see only locations below my locations) | Location | Filters the locations that can be viewed in EmpowerID to include only those below the assignee's locations | Empty |
Sample filter for Management Role (see only management roles in a list) | Management Role | Filters the management roles that can be viewed in EmpowerID to include only those specified | Empty |
Sample filter for Management Role (see only management roles in a location) | Management Role | Filters the management roles that can be viewed in EmpowerID to include only those in the location specified | Empty |
Sample filter for Management Role (see only management roles in or below my locations) | Management Role | Filters the management roles that can be viewed in EmpowerID to include only those in or below the assignee's locations | Empty |
Sample filter for Management Role Definition (see only management role definitions in a list) | Management Role Definition | Filters the management role definitions that can be viewed in EmpowerID to include only those specified | Empty |
Sample filter for Person (see only self) | Person | Assignees cannot view anyone in EmpowerID beyond their own person | Empty |
Users can have more than one Visibility Filter policy and you can use combinations of both to create policies that are as granular as needed. For example, you can use the above-mentioned Data Filter policy to allow users to only see people in their location and then add to a subset of those same users a Column Filter policy that replaces the PersonID attribute with "N/A." Users with both policies can see the same number of people; the difference is users with just the Data Filter policy can see email addresses, while users with both policies cannot.
When assigning multiple Visibility Filter policies like these to users, EmpowerID uses the following rules to determine filter precedence: