Managing Policy Sets

This section describes how to create, edit and delete policy sets.

Overview of Policy Sets

A policy set is a group of one approval policy and one records management policy that can be assigned to domains to define configurations and business rules for each associated domain. Policy sets should be designed to be reusable in a many to one fashion where each domain is assigned one policy set, but the policy set can be associated to many domains.

Create Policy Set

  1. Open Site Administration > Policy Management > Policy Sets

  2. Click add policy set, enter policy set name and description (optional)

  3. Click save

View and Edit Policy Set

  1. Click the view and edit link on the row of the policy set, OR click on policy set name

  2. View policy set details

  3. Edit policy set name and description and click save

Add Policies to Policy Set

Newly created policy sets use default approval and RMP policies automatically, though they won’t be displayed in the policy set details

If you wish to use either an approval or a records management policy other than the default policy, you can add policies to a policy set.

To add policies on policy set details:

  1. Select the desired policy dropdown (approval or records management)

  2. Search for a previously uploaded policy

  3. Select a policy and click save

Use the same process to change policies.

Add Domain to Policy Set

  1. On the policy set detail page, under Domains, click the dropdown

  2. Search and select one or more domains from the dropdown

  3. Click save

  4. You can search the linked domain list by domain name or page through

  5. You can also unlink domains from policy sets by clicking unlink icon on the same row as the domain name

Admin can select an already associated domain and will see a warning that this domain is already associated and can proceed to link to a new domain

Delete Policy Set

  1. Click on the delete link, on the same row as the policy set name

  2. Click confirm

Deleting a policy set that is already associated with a domain, will cause affected domains to use default policies. This will not affect the records already routed for approval. It will take effect on future records routed.