# Access certifications

Periodically review and re-certify which users have access to an application, and revoke access that is no longer needed.

Requires: workflows

> **Plan note:** Access certifications are part of workflows, available on the Advanced plan and above. See [Plans & add-ons](https://dts-identity.com/docs/getting-started/plans-and-addons.md).

An **access certification workflow** periodically re-checks who has access to an application and asks a reviewer to confirm it is still needed. Unlike an [approval flow](https://dts-identity.com/docs/workflows/approval-flows.md), which decides access *before* it is granted, a certification workflow runs on a recurring schedule *after* access already exists, so stale or forgotten access does not linger indefinitely.

You manage certification workflows under **Workflows → Access Certifications** in the Admin Console.

## Create a certification workflow

1. Open **Workflows → Access Certifications** and choose **Create Certification Workflow**.
2. Give the workflow a descriptive **name**.
3. On the **Settings** tab, choose:
   - **Review frequency** — how often a new campaign starts: monthly, quarterly, or yearly.
   - **Review period** — how many days a campaign stays open before it closes automatically.
4. The workflow has no rules until you add them, and it has no effect until it is assigned to an application.

## Add rules

A certification workflow's rules use the same **IF** conditions as an approval flow, but the outcome is different: instead of an approval decision, a rule names the **reviewers** who will be asked to re-certify access.

1. On the workflow's **Workflow rules** tab, select **Edit**, then **Create rule**.
2. Enter an optional **rule name**.
3. Define the **conditions** (all must match for the rule to apply):
   - **The user's directory is** — *any directory*, or one of a selected list of directories.
   - **The user's group membership includes** — *any group*, or at least one of a selected list of groups.
   - **The user is** — *any user*, or at least one of a named list of users, optionally with named users to **exclude**.
4. Choose who reviews: **Named reviewers** (a fixed list of users) or **Workspace responsibles**, the responsibles of the [workspace](https://dts-identity.com/docs/governance/workspaces.md) that contains the application, resolved when a campaign starts. A responsible never reviews their own access; if nobody else is left, that user is skipped.
5. Optionally tick **Activate rule after creation** so the rule takes effect once published.
6. Save the rule.

A rule with no reviewers is skipped: matched users are not included in a campaign until the rule has at least one reviewer. This also applies to **Workspace responsibles** when the application is not in a workspace or the workspace has no responsibles. A campaign whose matched users were all skipped this way is cancelled instead of closed, so it never counts as a completed review; a campaign with no matched users at all closes immediately.

As with approval flows, rule edits are kept as a **draft** until you **Publish** them. Publishing here works slightly differently from approval flows: **a campaign already in progress is not affected** — reviewers were notified based on the rules in effect when that campaign started. Published rule changes take effect starting with the *next* campaign.

## Assign a certification workflow to an application

1. Open the application and go to its **Policies** tab.
2. Under **Identity Governance**, enable **Access Certification** and select the workflow.
3. Save.

Removing the workflow from an application, or replacing it with a different one, cancels any campaign currently in progress for that application. Open reviews from the cancelled campaign are closed without affecting the reviewed users' access.

## How a campaign runs

Once a workflow is assigned to an application, campaigns start automatically (you can also start a scheduled one early, see below):

1. A campaign is **scheduled** for the application, timed by the workflow's review frequency (immediately for a newly assigned application, or after the workflow's frequency has elapsed since the last campaign).
2. When the scheduled start is reached, the campaign becomes **active**: one review is created for every employee with access to the application, whether granted directly, through an assigned group, or through an assigned directory. Each user is matched against the workflow's rules to determine their reviewer, and each reviewer is notified by email. Only employees are reviewed; customer and consumer accounts are not included.
3. Reviewers **certify** or **revoke** access for each user (see below) until the campaign's review period elapses.
4. When the review period ends, the campaign **closes**. Any review that was not decided in time is marked **not reviewed in time** — the affected user's access is left unchanged.

You can start a scheduled campaign ahead of its planned date with **Start early** on the Campaigns tab: reviews are created and reviewers notified right away, rather than waiting for the next cycle. This is useful for an off-cycle review.

You can end an active campaign before its due date with **End early** on the Campaigns tab: the campaign closes immediately, decisions already made are kept, and any open reviews are marked not reviewed in time. The next campaign is scheduled as usual.

You can see the full history and current progress of an application's campaigns on the workflow's **Campaigns** tab (application, status, start date, due date, and how many reviews were certified, revoked, or left unreviewed). A campaign also shows how many revoked reviews still need manual follow-up (see below).

The **Workflows** main page highlights campaigns that need attention across all workflows: those currently running, any that are overdue, and any with unresolved manual follow-ups. The section only appears when there is something to act on; scheduled and cleanly closed campaigns stay on their workflow's Campaigns tab.

## Review access

Reviews appear in the same place as approval requests: **Your tasks** and **Approvals → Open & active**, under an **Active access reviews** section, for whichever reviewers a matching rule named. Decided reviews move to **Approvals → Closed** under **Closed access reviews**.

For each review you are a reviewer on, two actions are available:

- **Certify** — confirms the user still needs access. No change is made to their access.
- **Revoke** — removes the user's access to the application, with an optional reason. If the application provisions accounts automatically, the user is deprovisioned there as well.

Nobody certifies their own access: if a named reviewer is also the reviewed user, **Certify** is refused for them and another reviewer has to decide; revoking stays possible. If they are the only reviewer, the review stays open until the campaign closes.

### What revoke does and does not do

Revoke can only remove a **direct** assignment of the application to the user. If the user's access comes (also or only) from an assigned **group** or **directory**, that access cannot be removed automatically — doing so would affect every other member. The review is flagged **Manual remediation required** so you can follow up at the source (remove the user from the group, or adjust the group's or directory's own assignment). The flag is shown on the review itself (in the closed reviews list and its details), counted on the workflow's Campaigns tab and the Workflows main page, and recorded in the audit log. Each review also shows the access path (direct, or via which group or directory) so you can see why a user has access.

All open follow-ups are collected under **Approvals → Remediations**, so you can see everything that still needs action across all campaigns at a glance (the tab shows the count). Each entry shows the affected user and the group or directory their access comes from. Open follow-ups from your own revoke decisions also appear in **Your tasks**, next to reviews still waiting on you. You can also click a campaign's manual-remediation count (on the overview or the Campaigns tab) to open the same list scoped to that campaign.

Once you remove the underlying access (take the user out of the group, or adjust the group's or directory's assignment), the flag clears on its own: the review is marked **Remediation resolved** and drops out of the counts. No manual confirmation step is needed, the status reflects whether the user still has access.

## Reference

### Review frequencies

| Frequency | A new campaign starts |
|---|---|
| Monthly | Every month after the previous campaign started |
| Quarterly | Every three months after the previous campaign started |
| Yearly | Every year after the previous campaign started |

### Campaign statuses

| Status | Meaning |
|---|---|
| Scheduled | Waiting for its start date |
| Active | Reviews are open for decision |
| Closed | The review period ended (or the campaign was ended early); undecided reviews were marked not reviewed in time |
| Cancelled | The workflow was unassigned or deleted before the campaign closed, or none of the matched users had a reviewer |

### Review outcomes

| Outcome | Effect |
|---|---|
| Certified | Reviewer confirmed access is still needed; no change |
| Revoked | Reviewer removed the user's direct access (and deprovisioned it where applicable); group- or directory-based access is flagged for manual follow-up instead |
| Not reviewed in time | The campaign closed before a reviewer decided; access is left unchanged |

## Troubleshooting

- **No campaign ever starts for an application.** Check that a certification workflow is assigned on the application's Policies tab, that the workflow has at least one active rule with reviewers selected, and that the application has employees with access (directly, or through an assigned group or directory). Customer and consumer accounts are not reviewed.
- **Revoking a review did not remove the user's access.** The user's access comes from a group or directory, not a direct assignment, so it cannot be removed automatically. The review is flagged **Manual remediation required**: remove the user from the group, or adjust the group's or directory's own assignment, instead.
- **A reviewer cannot act on a review.** Only the reviewers named by the matching rule can decide it, and they need access to the Admin Console. Adjust the rule's reviewers if the wrong people were notified.
- **The application can't select a certification workflow.** This requires the **workflows** feature on your plan and at least one certification workflow to exist. Create a workflow first, then assign it on the application.

## Related

- [Approval flows](https://dts-identity.com/docs/workflows/approval-flows.md) — gating access before it is granted
- [Approvals](https://dts-identity.com/docs/workflows/approvals.md) — the shared inbox where reviews and approval requests are decided
- [Your tasks & approvals](https://dts-identity.com/docs/getting-started/your-tasks-and-approvals.md) — where reviews waiting on you appear
- [Applications](https://dts-identity.com/docs/integrations/applications.md) — assigning a certification workflow to an application
- [Audit logs](https://dts-identity.com/docs/monitoring/audit-logs.md) — the permanent record of certification decisions
