Admin Guides / Access review campaigns
Run a campaign
Launch a campaign, follow it while reviewers work, carry out the removals and close it.
Launch a campaign
A scheduled definition launches on its own when the Warde campaign scheduler job runs, daily at 06:30 instance time. To launch one now, open the definition in the Admin Workspace and select Launch campaign; that works for any active definition, scheduled or on demand, and does not move its next scheduled run.
The campaign is named after the definition, with the launch date. It shows Generating while Warde builds the review lines in the background, which for a large scope takes a few minutes, then Active.
A definition has one live campaign at a time. A launch, by hand or on schedule, is refused while the last one is still running, because two runs would give the same access to two reviewers.
While a campaign runs
When a campaign launches, Warde freezes its scope, reviewers and rules, creates one review task per reviewer, and emails each reviewer Access review assigned to you. The email links to the review on My Access.
| When | What happens |
|---|---|
| Before the due date | Reviewers are reminded the number of days before set in Guided Setup (default 3) |
| After the due date | The review is escalated to the reviewer's manager after the days set in Guided Setup (default 3). The manager can complete it. |
| A reviewer hands it on | Reassign review moves the whole review to someone better placed, and the hand-over is recorded |
| A reviewer is on leave | Platform delegates of the reviewer can work it, and decisions are recorded under the delegate's own name |
The Admin Workspace's Access reviews dashboard shows running campaigns, reviews past their due date, undecided lines, and removals not yet confirmed.
Removals
A Remove decision is carried out the way Guided Setup step 11 says: directly, or through a removal request every time, or only when the work is manual. Either way the removal goes to the engine, or to the collection's support group as a ServiceNow task.
- The access shows Pending revoke until the engine confirms the removal or the task is closed complete.
- If a removal fails, the access stays as it was and the campaign waits.
- Cancelling the removal in triage reopens the decision, so the reviewer can decide again.
- Removing one piece of access never removes other access linked to it.
A campaign moves from active to closing when every line is decided, and to complete when every removal is confirmed. Cancel campaign stops a campaign, but removals already sent are not taken back.
Reopen decision on a review line sets it back to not decided. It is not available while the line's removal can still run (cancel the operation first), after the removal is confirmed, or once the campaign has closed.