Why run an access review campaign?
Access review campaigns help Security and IT teams to securely control what software users can access, all while making sure employees can also successfully complete their work. From a least privilege and security perspective, ensuring that users only have the access they need, for only as long as they need it, reduces the access footprint of your company for sensitive systems and data. Running regular access review campaigns also helps you to achieve compliance with security standards and audit requirements.View all campaigns
On the Campaigns page, campaigns are sorted by state and type:- Running campaigns are currently in progress.
- Draft campaigns have not yet started.
- Completed campaigns have ended.
- Templates are saved campaign outlines used to create one-time or recurring scheduled campaigns.
How do campaign templates work?
If there’s a campaign pattern you use repeatedly, create a reusable campaign template instead of configuring the same campaign from scratch every time.
Create a new campaign
Follow this process to create a single campaign. Jump to Create a campaign template to set up a template that can be used to create many similar campaigns. C1 offers four ways to define what a campaign covers:- By entitlements — Select specific entitlements, apps, or entitlement types to review. This is the standard approach and works for any app in C1.
- By access conflicts — Review access that has triggered violations in your conflict monitors. Choose Access conflicts as the review type in Step 1 below.
- By inheritance — Scope the campaign to resources and role assignments in a cloud infrastructure app, and let C1 resolve all access that flows into them through the resource hierarchy. See Scope an access review campaign by inheritance for details.
- By users (early access) — Scope the campaign to specific users, and let C1 find the access those users hold when you stage the campaign. See Scope an access review campaign by users for details.
Step 1: Set up the campaign
- Name: The campaign’s name, which will be displayed to reviewers and shown in the campaign list view.
- Description: The description of what this campaign entails and any directions you want to deliver to reviewers.
- Campaign type: Select Single instance, then set the Due date for the campaign.
-
Review scope type: Select how the campaign will identify what to review:
- By entitlements: Review user access to specific entitlements or applications. This is the most common type of campaign.
- By access conflicts: Review user access that has triggered a violation in one of your enabled conflict monitors. This is a great option for quickly remediating high-risk access issues identified by your conflict monitors.
- By inheritance: Review access to cloud infrastructure apps by selecting resources and role assignments. C1 resolves all access that flows into your selections through the resource hierarchy, including inherited and group-based access. See Scope an access review campaign by inheritance for details.
- By users (early access): Review the current access of specific users, without selecting apps, entitlements, or resources. C1 finds the access those users hold when you stage the campaign. See Scope an access review campaign by users for details.
- Owner: The campaign’s owner, who will manage the campaign while it is in progress. You can set more than one campaign owner. Each owner must have the Campaign Administrator or Super Administrator user role in C1.
- Review policy: The campaign’s default review policy. If needed, you’ll be able to adjust the policy to be used for the review of individual entitlements later in the campaign creation process.
Step 2: Configure how the campaign will run
- By application: review access to one application at a time
- By resource: review access organized by resource, so you can see all access across a resource tree in one place
- By user: review one user’s access at a time
- Unstructured: all the assigned reviews together in one list
- To automatically start the campaign on a specific date and time, click to turn on Automatically start campaign, then set the scheduled start date.
- If the campaign is set to automatically start, choose whether to proceed with auto-start if there are unresolved campaign data accuracy issues. Campaign owners will be notified of any data accuracy issues when they are discovered.
- To automatically end the campaign on a specific date, click to turn on Automatically end campaign, then set the date.
- If the campaign is set to automatically end, choose whether incomplete reviews will be revoked or skipped when the campaign ends.
- Notify all reviewers with assigned review tasks when the campaign begins
- Notify all campaign owners and reviewers when the campaign ends
- When the campaign is complete, generate a campaign report and notify all campaign owners when it’s ready for download
Step 3: Choose what to review
Next, build a list of the resources that your campaign will review.- Users only (default) — Review access grants held directly by users.
- Resources only — Review access grants held by groups or roles instead of users.
- Users and resources — Review access grants held by either users or groups/roles.
- To run a UAR on user access to specific permissions, click Entitlements and make your selections, then click Save. When selecting specific resources, you can use the filter bar to narrow results by Application, entitlement type, Risk level, and Compliance framework. Select one or more values for any filter to find matching entitlements. Filters use OR logic within a single filter type and AND logic across filter types. For example, selecting risk levels “High” and “Critical” along with compliance framework “SOX” returns entitlements that are (High OR Critical) AND (SOX). OR
- To run a UAR on user access to applications, click Application access and select apps, then click Save. OR
- To run a UAR on all of the entitlements of a given type within a specific app (such as all the groups within Google Workspace), click Entitlements by type and make your selections, then click Save. OR
- To select entitlements by attribute instead of choosing them one by one, click Custom selectors, add filters, then click Save. For example, select every entitlement in Okta, or only Okta groups with a high risk level. The criteria are evaluated when you prepare the campaign, so the campaign includes every entitlement that matches at that time, including ones added after you set up the campaign. See Build a custom selector for the available filters.

- Click Select specific users to build a list of users whose access will be reviewed, then click Save. OR
-
Click Select users by criteria to review users who match the criteria you set, then click Save.
You can mix and match these options:
- User status in C1
- Direct reports of a manager
- User profile attributes. For example, to run an access review campaign on all the AcmeApp users in your company with the job title “Engineer”, create the parameter User AcmeJob is Engineer.
- Exclude users in specific groups from the campaign
- Click CEL expression to enter a CEL expression that describes the users you want to review. The expression must return a list of users to be valid.
-
Click Select accounts by criteria to review app accounts that match the criteria you set, then click Save.
You can mix and match these options:
- No account owner
- Account status
- Account type
- Account domain (specifically, whether the email address associated with the account has been marked trusted by a C1 admin at your organization)
- Click CEL expression to enter a CEL expression that describes the accounts you want to review. The expression must return a list of accounts to be valid.
-
Click Select grants by criteria to review only the access grants that match the criteria you set, then click Save.
You can mix and match these options:
- New grants added within the time period you select or between two specific dates
- Temporary (time-limited) or permanent grants
- Grants by usage, using Unused in the last or Used in the last (this information is not available for all applications). See Filter grants by usage.
- Direct grants (permissions assigned directly to users) or inherited grants (permissions assigned to a group or role, which are “inherited” by users assigned to that group or role)
- Grants sourced from access profiles (check the box to exclude these grants from your campaign)
Build a custom selector
A custom selector describes the entitlements to review as a set of filters instead of a hand-picked list. Click Add filter to add a filter, and click it again to add the next one. The Match all filters panel lists the filters you’ve added, and Preview entitlements shows the entitlements that currently match. An entitlement is included when it matches every filter in the panel. Within a single filter, matching any one of its values is enough.., _, /, and -.
The criteria are evaluated when the campaign is prepared. The campaign creation assistant can set these filters when it builds a campaign for you.
Filter grants by usage
Use the Grant usage setting under User grant selection > Select user grants by criteria to review grants based on whether the account has recently used the app. C1 bases usage on each account’s last login to the app, and accounts with no login data are left out of any usage filter.- Select Unused in the last and choose a period to review only grants that haven’t been used in that time, such as when you’re cleaning up unused access.
- Select Used in the last and choose a period to review only grants that have been used in that time.
- Select both to review grants last used between the two periods. The Used in the last period must be longer than the Unused in the last period. For example, Used in the last 90 days and Unused in the last 30 days reviews grants last used between 30 and 90 days ago.
Exclude entitlements from a campaign
Use Excluded entitlements when you want to review most of what a scope covers but skip a few entitlements. Instead of selecting everything else by hand, you list what to leave out, and the list stays accurate as new entitlements appear. The Excluded entitlements section appears on the Scope tab for these campaign scope types:- By entitlements campaigns that use Custom selectors or Entitlements by type. It doesn’t appear when you select Application access or specific Entitlements, because you’ve already chosen exactly what to include.
- By access conflicts campaigns. Until you add exclusions, the campaign reviews every eligible entitlement in the selected conflict monitors. If you exclude one side of a conflict, C1 still reviews the other side, so the access that remains gets certified. To learn about conflict monitors, see Detect access conflicts.
- By inheritance campaigns. See Exclude entitlements from an inheritance campaign.
- Entitlements to pick specific entitlements to leave out. Each excluded entitlement is listed on its own row, with its application, entitlement, description, and grant count, so you can review the list and remove one entitlement without affecting the others. OR
- Custom selector to leave out every entitlement that matches a set of filters. The filters are the same as in Build a custom selector, and an entitlement is excluded when it matches all of them.
- Exclusions are evaluated when the campaign is prepared. A custom selector exclusion also leaves out matching entitlements that are added later.
- Exclusions carry over when you duplicate a campaign or create one from a template. They also appear in the Validate scope report and in campaign reports.
- Ownership entitlements aren’t listed in the entitlement picker.
- The number of entitlements you can exclude counts against the same per-campaign limit as the entitlements you include. If you reach the limit, use a custom selector instead of listing entitlements one by one.
Step 4: Check data accuracy
If any of your selections are sourced from connectors or file uploads that have not been updated recently, you’ll see an indicator and a Your campaign might have data accuracy issues banner on the Accuracy tab.
- A connector hasn’t synced for more than two days
- A file source hasn’t been updated in more than seven days
- A connector errored during the most recent sync
Step 5: Stage the campaign
Step 6: Start the campaign
If you’ve set up the campaign to automatically start, it will launch on the scheduled date. If not (or if you need to start the campaign sooner than the scheduled start date), follow these steps to start the campaign when you’re ready:Create a campaign with the Campaign assistant
Instead of working through each step yourself, click Create with Campaign assistant on the Campaigns page and describe the access review you need in plain language — for example, “Review all Salesforce access granted in the last 90 days” or “Set up a quarterly review of admin roles in Okta.” The assistant configures the campaign’s policy, owners, and scope based on your description. Review what it sets up, make any adjustments you need, then follow the same validate, stage, and start steps as above.Duplicate a past campaign
Instead of creating a campaign from scratch, you can save time and effort by duplicating a past campaign and tailoring it to your current needs. Duplicating a campaign is a quick way to reuse a past campaign’s settings for a one-off review. If you need to run similar campaigns on a regular schedule, create a campaign template instead.Create a campaign template
Step 1: Set up the template
- Name: The campaign’s name, which will be displayed to reviewers and shown in the campaign list view.
- Description: The description of what this campaign entails and any directions you want to deliver to reviewers.
- Campaign type: Select Template, then set the Campaign duration, or how long each campaign created from the template will run.
-
Review scope type: Select how campaigns created from this template will identify what to review:
- By entitlements: Review user access to specific entitlements or applications. This is the most common type of campaign.
- By access conflicts: Review user access that has triggered a violation in one of your enabled conflict monitors. This is a great option for quickly remediating high-risk access issues identified by your conflict monitors.
- By inheritance: Review access to cloud infrastructure apps by selecting resources and role assignments. C1 resolves all access that flows into your selections through the resource hierarchy, including inherited and group-based access. See Scope an access review campaign by inheritance for details.
- By users (early access): Review the current access of specific users, without selecting apps, entitlements, or resources. C1 finds the access those users hold when you stage the campaign. See Scope an access review campaign by users for details.
- Owner: The campaign’s owner, who will manage the campaign while it is in progress. You can set more than one campaign owner, just be sure anyone you add has the Campaign Administrator or Super Administrator user role in C1.
- Review policy: The campaign’s default review policy. If needed, you’ll be able to adjust the policy to be used for the review of individual entitlements later in the campaign creation process.
Step 2: Configure how campaigns created from this template will run
You can set the template to create instances of the campaign on a date in the future or on a recurring schedule. You can also create an on-demand instance of the campaign at any time.- By application: review access to one application at a time
- By resource: review access organized by resource, so you can see all access across a resource tree in one place
- By user: review one user’s access at a time
- Unstructured: all the assigned reviews together in one list

- To automatically start each campaign, click to turn on Automatically start campaign. Campaigns will auto-start two days after they are created from this template.
- If the campaign is set to automatically start, choose whether to proceed with auto-start if there are unresolved campaign data accuracy issues. Campaign owners will be notified of any data accuracy issues when they are discovered.
- To automatically end each campaign on the scheduled end date calculated from the campaign duration you set, click to turn on Automatically end campaign.
- If the campaign is set to automatically end, choose whether incomplete reviews will be revoked or skipped when the campaign ends.
- Notify all reviewers with assigned review tasks when a campaign begins
- Notify all campaign owners and reviewers when a campaign ends
- When a campaign is complete, generate a campaign report and notify all campaign owners when it’s ready for download
Step 3: Choose what to review
Next, build a list of the resources that campaigns made from this template will review.- Users only (default) — Review access grants held directly by users.
- Resources only — Review access grants held by groups or roles instead of users.
- Users and resources — Review access grants held by either users or groups/roles.
- To run a UAR on user access to specific permissions, click Entitlements and select resources, then click Save. When selecting specific resources, you can use the filter bar to narrow results by Application, entitlement type, Risk level, and Compliance framework. Select one or more values for any filter to find matching entitlements. Filters use OR logic within a single filter type and AND logic across filter types. For example, selecting risk levels “High” and “Critical” along with compliance framework “SOX” returns entitlements that are (High OR Critical) AND (SOX). OR
- To run a UAR on user access to applications, click Application access and select apps, then click Save. OR
- To run a UAR on all of the entitlements of a given type within a specific app (such as all the groups within Google Workspace), click Entitlements by type and make your selections, then click Save. OR
- To select entitlements by attribute instead of choosing them one by one, click Custom selectors, add filters, then click Save. For example, select every entitlement in Okta, or only Okta groups with a high risk level. The criteria are evaluated each time you prepare a campaign from the template, so new entitlements that match are included automatically without editing the template. The filters work the same way as in campaigns; see Build a custom selector.

- Click Select specific users to build a list of users whose access will be reviewed, then click Save.
-
Click Select users by criteria to review users who match the criteria you set, then click Save.
You can mix and match these options:
- User status in C1
- Direct reports of a manager
- User profile attributes. For example, to run an access review campaign on all the AcmeApp users in your company with the job title “Engineer”, create the parameter User AcmeJob is Engineer.
-
Click Select accounts by criteria to review app accounts that match the criteria you set, then click Save.
You can mix and match these options:
- No account owner
- Account status
- Account type
- Account domain (specifically, whether the email address associated with the account has been marked trusted by a C1 admin at your organization)
-
Click Select grants by criteria to review only the access grants that match the criteria you set, then click Save.
You can mix and match these options:
- New grants added within the time period you select or between two specific dates
- Temporary (time-limited) or permanent grants
- Grants by usage, using Unused in the last or Used in the last (this information is not available for all applications). See Filter grants by usage.
- Direct grants (permissions assigned directly to users) or inherited grants (permissions assigned to a group or role, which are “inherited” by users assigned to that group or role)
- Grants sourced from access profiles (check the box to exclude these grants from your campaign)
Dynamic scope re-evaluation for tag-filtered templates
When you use risk level or compliance framework filters to select entitlements for a campaign template, C1 saves the filter criteria rather than a fixed list of entitlements. Each time a campaign is created from the template and prepared, the system re-evaluates the tag criteria against the current state of your entitlements. This means:- Entitlements that have been tagged since the template was last configured are automatically included in the next campaign.
- Entitlements that have had tags removed are automatically excluded.
- You do not need to manually update the template scope when entitlement tags change.
Step 4: Review and start a campaign created from a template
When a new campaign is created from the template, it is shown on the template’s Campaigns tab and also added to the Drafts tab. Edit the campaign as needed, then follow Steps 4 through 6 in Create a new campaign to review current data accuracy, stage the campaign, and start the campaign (if necessary).Frequently asked questions about creating campaigns
What happens if I add an empty entitlement to the campaign?
What happens if I add an empty entitlement to the campaign?
Can I add or edit campaign instructions once the campaign is underway?
Can I add or edit campaign instructions once the campaign is underway?
What happens when new entitlements are tagged after I set up a tag-scoped campaign template?
What happens when new entitlements are tagged after I set up a tag-scoped campaign template?
Can I combine tag-based scope with manually selected entitlements?
Can I combine tag-based scope with manually selected entitlements?
What tag types can I use for scoping campaigns?
What tag types can I use for scoping campaigns?
Can I change the scope type after creating a campaign?
Can I change the scope type after creating a campaign?
What happens if I select 'All' conflict monitors and a new monitor is enabled later?
What happens if I select 'All' conflict monitors and a new monitor is enabled later?