Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

EmpowerID offers a powerful policy engine that you can use to write policies that give users the opportunity to request access to targeted IT resources like shared folders, Office 365 licenses, group membership, roles, and more. These policies, known as “Eligibility policies,” enhance your organization’s security and benefit end-users both by shielding your organization’s most sensitive roles and resources from unnecessary exposure while giving users a simpler and less distracting “IT Shop” experience that targets each of those users with a streamlined catalog of resources from which they may pick and choose. Simply put, Eligibility policies allow you to control what IT resources users may see and request when shopping in the IT Shop. Eligibility policies are extremely flexible and can be written against any resource and applied to users by attribute query, role membership, group membership, or other criteria. This makes it easy to target who receives which policies for what resources and have the assignment automated and maintained through its lifecycle. To further ease the administrative burden, Eligibility policies can be applied to all requestable items of a type by location in addition to one by one. This allows policies to be broader granting or excluding eligibility using the EmpowerID Location tree. For roles, eligibility policies can be applied to their members to control what they may see and request in the IT Shop. Policies also apply to the role itself as a possible IT Shop item.

Eligibility Rules

Eligibility policies can be defined with rules known as “Inclusion” and “Exclusion.” Inclusion rules define the items a user is authorized to see and request in the IT Shop and ensure these items are only the ones that would make sense for them to request. An application example could be using rules to filter the type of applications and other resource types available for sales employees and developers. The catalog of requestable resources available to each of those employees should be different to ensure that unwarranted access requests are not generated. Additionally, inclusion and exclusion rules help organizations provide employees a more pleasant user shopping experience as they are shielded from viewing resources that they cannot request. 

...

Easy html macro
theme{"label":"solarized_dark","value":"solarized_dark"}
contentByMode{"html":"<!doctype html>\r\n<head>\r\n<link href=\"https://cdn.jsdelivr.net/npm/bootstrap@5.1.0/dist/css/bootstrap.min.css\" rel=\"stylesheet\" integrity=\"sha384-KyZXEAg3QhqLMpG8r+8fhAXLRk2vvoC2f3B09zVXn8CA5QIVfZOJ3BCsw2P0p/We\" crossorigin=\"anonymous\">\r\n</head>\r\n<nav aria-label=\"...\">\r\n <ul class=\"pagination justify-content-center\">\r\n <li class=\"page-item\">\r\n <a class=\"page-link\" href=\"https://dotnetworkflow.jira.com/wiki/spaces/EIDIGACoreacessselfservice/pages/2387742560/Access+Assignment+and+Delegation2461532180/Publish+Items+to+the+IT+Shop\" target=\"_top\"> &laquo; &nbsp;&nbsp;Previous</a>\r\n </li>\r\n <li class=\"page-item active\" aria-current=\"page\">\r\n <span class=\"page-link\">Current</span>\r\n </li>\r\n <li class=\"page-item\">\r\n <a class=\"page-link\" href=\"https://dotnetworkflow.jira.com/wiki/spaces/EIDIGACoreacessselfservice/pages/2458681478/2387742605Configure+Eligibility\" target=\"_top\"> Next&nbsp;&nbsp; &raquo;</a>\r\n </li>\r\n </ul>\r\n</nav>","javascript":"","css":""}