Versions Compared

Key

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

Provisioning Policies allow you to automate the provisioning, moving, disabling, and de-provisioning of resources for users based on their roles, memberships, and locations within your organization.

This topic demonstrates the following:

  • How to create a provisioning policy that provisions home folders

  • How to assign the provisioning policy to an EmpowerID actor type

Info

Prerequisites

  • EmpowerID must first be connected to Active Directory. For details, see Connecting to Active Directory.

  • RET provisioning and RET deprovisioning must be enabled on the Active Directory account store.

  • A File server must be added to EmpowerID as a managed resource system. For details, see Adding File Servers.

Tip

Provisioning policies can be targeted against any number or combination of Management Roles, groups, Business Roles and Locations, Query-Based collections, as well as individual people.

How to create a provisioning policy for Home Folders

  1. n the navbar, expand Identity Lifecycle and select Provisioning Policies (RETs).

  2. On the Policies page, click the Add button at the top of the grid.

     

  3. Under Choose Type, select Windows Home Folder from the Object Type To Provision drop-down.

  4. In the General section of the form fill in the following fields:

    1. Name – Enter a name for the policy.

    2. Description – Enter a description for the policy.

    3. Directory – Select the inventoried Active Directory account store.

    4. Profile Drive Letter – Select the drive where home folders created by the policy are to be located.

    5. Share Folder – Specify whether the folder is a shared folder.

    6. Share as Hidden – Specify whether the share should be hidden.

  5. In the Throttling Settings section of the form, specify the provisioning and deprovisioning thresholds for the policy. These settings are as follows:

    • All Provisions Require Approval – If this option is selected, the provisioning of each RET specified by the policy will need to be approved by a user delegated access to the Resource Entitlement Inbox.

    • All Deprovisions Require Approval – If this option is selected, the deprovisioning of each RET specified by the policy will need to be approved by a user delegated access to the Resource Entitlement Inbox.

    • Require Approval if Provision Batch Larger Than Threshold – This field allows you to set a numeric value that needs to be reached by a single run of the Resource Entitlement Inbox before an approver needs to approve the provisions. If the threshold is reached, EmpowerID will not provision any of the Salesforce user accounts until approval is granted.

    • Require Approval if Deprovision Batch Larger Than Threshold – This field allows you to set a numeric value that needs to be reached by a single run of the Resource Entitlement Inbox before an approver needs to approve the deprovisions. If the threshold is reached, EmpowerID will not deprovision any of the Salesforce user accounts until approval is granted.

  6. In the Advanced section of the form, do the following:

    1. Select a desired option from the On Claim Action drop-down. You have the following options:

      • Do Nothing – No action occurs. This tells EmpowerID to simply mark any previous resources assigned to the user that match this policy as RET-managed resources. For example, if the user already has a home folder and is placed in a Management Role targeted by the RET policy, EmpowerID marks that user's home folder as RET managed.

      • Publish Workflow Event – Executes custom workflow code.

    2. Select a desired option from the On Revoke Action drop-down. You have the following options:

      • Do Nothing – No action occurs.

      • Publish Workflow Event – Executes custom workflow code.

  7. Click Save to create the policy.

  8. After EmpowerID creates the policy, you should be directed to the completed Policy Details page for the policy.

Next, assign the policy you just created to one or more targets as demonstrated below.

How to assign the provisioning policy

  1. On the Policy Details page, click the Find Policies breadcrumb. 


  2. Search for the policy you just created and then click the Display Name link for it.


    This directs you to the View page for the policy. This page allows you to manage the policy as needed. 


  3. On the View page, click the Assignees accordion to expand it. This accordion allows you to assign the policy to any or the following EmpowerID actor types:

    • Business Roles and Locations – All people in the selected Business Role and Location combinations receive the resource granted by the policy.

    • Management Roles – All people in the selected Management Roles receive the resource granted by the policy.

    • Management Role Definitions – All Management Roles that are children of the selected Management Role Definition receive the resource granted by the policy.

    • Query-Based Collections (SetGroup) – All people in the selected collection receive the resource granted by the policy.

    • Groups – All people in the selected groups receive the resource granted by the policy.

    • People – All people selected receive the resource granted by the policy.

  4. From the Assignees accordion, click the Add button above the assignee type to which you are making the assignment.

  5. In the Add Entry pane that appears, search for and select the appropriate assignee.

  6. Enter a number to specify the priority for the RET policy in the Priority field. This value is used to determine the priority of the RET if the user qualifies for the same RET via another assignment, such as being a member of a group that has the same policy. The lower the number, the higher the priority. 

  7. Click Save.

  8. Back in the main form, click Save.

Insert excerpt
IL:External Stylesheet - v1
IL:External Stylesheet - v1
nopaneltrue

Div
stylefloat:left; position:fixed;
idarticleNav

IN THIS ARTICLE

Table of Contents
maxLevel4
minLevel2
stylenone
printablefalse