$ every product image on this site is an unretouched screenshot of the running platform — demo tenant, fictional people, captured live
✅ Platform · Certify

Reviews that fire when
something changes.

Continuous rolling reviews, classic campaigns, and event-triggered reviews that start the moment a transfer or new grant happens — not at the next quarterly scramble.

Continuous · campaign · event

The review starts when the risk starts.

A mover carries access into a new role today — so the review of that access starts today. Continuous rules re-check on a rolling clock; campaigns bundle reviews for audit season; events catch changes the moment they happen.

  • Event reviews on transfers, new grants, emergency access use, and role or policy content changes
  • Reviews grouped per account — where shared and privileged risk lives
  • Coverage in three states, not two: covered, no rule, or a rule that resolves to nobody. A green tick nobody stands behind is worse than a visible gap
  • And the round announces itself: assignment and due-soon are two separate mails, not a login habit — with the same single decide link the approval mail carries, per tenant and off by default. Reminders on overdue items fire from a scheduled job; nobody "runs the remind round" by hand
app.rapidvalue.eu/certifications
the review dashboard — open items, progress per review, and reviewers running behind
the review dashboard — progress per review, and who is running behind

Decisions with context

Reviewers see enough to decide — and can't review themselves.

Each item shows the person, the access, its provenance and last use. Self-review is blocked server-side; reviewer chains support quorums and reassignment, and every outcome lands on the immutable trail.

  • Account-first review scope: judge the account, decide its grants together
  • Self-review guard, enforced in the service and not just the screen — you can never certify your own access. Attesting your own ownership is the one deliberate exception
  • The owner attestation names the thing — "Owner attestation: Salesforce", never ": application" — and "no" is a real answer: name the successor and the handover moves their pending decisions at that moment, or disclaim and the object lands in the orphan queue instead of a flag nobody reads
  • Deadline actions per kind: revoke, disable, flag, or suspend
  • A reviewer with forty look-alike lines decides them in one action — over access requests and all three certification shapes — with a shared note and a confirmation that says how many, not a toast that hides which three failed
  • A review item whose question disappeared closes itself as superseded, with the reason recorded. We measured 24 of 192 open items asking a question that had already been settled
…/access-reviews · campaigns
a campaign in flight — decided, kept and revoked, and who still owes a decision
a campaign in flight — kept, revoked, and who still owes a decision

See a review running on your own data.

A 30-minute kickoff connects your HR feed and one system — working POC the same day.

Bring your HR feed plus one system you trust us to read — that is all the kickoff needs. No NDA, no second call with a sales engineer, no procurement form.