Portal User Guide › Running Certification Campaigns › How to Use Campaigns

How to Use Campaigns

You can customize certification processes to support many business needs. The basic campaign process follows this general pattern:

1. A role engineer or high-level administrator defines the campaign in CA RCM based on business needs. The campaign owner specifies the following information for the campaign:
   • The universe on which the campaign is based, and additional data such as audit cards and member lists that the campaign uses.
   • Filters that reduce the scope of the campaign to a subset of entities or links in the configuration.
   • How the campaign identifies certifiers for each entity under review.
   • How to handle changes made by reviewers.

   CA RCM creates the campaign, and automatically assigns the entities and links under review to managers and administrators in the enterprise.

2. When the campaign launches, CA RCM sends these managers email invitations that include links to the CA RCM server. On the server, managers use a ticket-based task management system to review and certify the entities and links assigned to them.
3. When certifiers reject existing links or suggest new links, the configuration must be changed. CA RCM contacts the managers of the entities involved, and requests approval of the change. These approval tasks are also managed using the ticket-based system. Approved changes are then implemented in the target configuration.

Example: Certify User Privileges Following an Acquisition

Companies commonly use certification campaigns to review and certify the roles and resources assigned to each user. In this example, new users and resources were added to the CA RCM model configuration following an acquisition. Administrators run a certification campaign to verify the privileges assigned to these new users.

The stages of the campaign are as follows:

1. The role engineer creates a campaign that certifies user entities and their links. The role engineer defines user attribute filters that limit the scope of the campaign to the new employees. A member list maps managers to the new users and resources.
2. Each manager reviews the privileges assigned to their workers. Bob Smith reviews the privileges given to Hector Torres, and suggests access to a database that Hector needs in his new position.
3. CA RCM sends an email to Deepak Chamarti, the owner of the database. Deepak approves the change, and CA RCM updates the configuration. Hector Torres now can access the database.