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

Access requests people
actually understand.

A request catalog scoped to what each user may see, approval chains you design visually, and delegation that keeps decisions flowing when someone's away.

See it on your own data → See it in the tour

Request access

A shop window, scoped per person.

Users request access from a catalog filtered by audience rules — they only see what they're allowed to request. SoD conflicts are checked before the request even reaches an approver.

  • Requestability cascades: system → application → type → entitlement
  • Multi-step approval chains with quorums (all / any / N-of-M)
  • Self-approval is auto-detected and auto-resolved — no rubber-stamping your own request
app.rapidvalue.eu/access-request
the request catalog — scoped to what you may see
the request catalog — scoped to what you may see

Approvals & delegation

Who requested what, for whom — in words.

Approvers see the request in business language with the requestor, subject and remaining chain spelled out. Out-of-office? Delegate your queue for a period — decisions taken on your behalf stay visibly badged and separately auditable.

  • One inbox for approvals, reviews and exceptions
  • OOO and standing delegations, scoped by work type
  • "On behalf of" badge — the trail never loses who actually decided
…/approvals
the approvals inbox — in words, not IDs
the approvals inbox — in words, not IDs

One rule model, central defaults, local overrides

Define a chain once. Override only where it differs.

Reviewer chains are named, reusable objects with per-type defaults: approval rules, review rules and role formalization all resolve through the same registry — inline override first, then the named chain, then the default for that type, then the manager as the universal fallback. No rule can end up with silently nobody to decide.

  • Named chains with quorums (all / any / N-of-M), reused across every rule workbench
  • Per-type defaults — a rule without a chain still gets the right reviewer
  • Every workbench overrides locally, never by copy-paste
…/governance-settings · reviewer chains
the reviewer-chain registry — named chains, per-type defaults, quorums
the reviewer-chain registry — named chains, per-type defaults, quorums

Related

Related

Roles & role mining

Roles make requests coarse-grained and reviewable.

Read more → Related

Segregation of duties

Toxic combinations are checked at request time.

Read more → Related

Access reviews

What was granted gets re-checked, continuously.

Read more →

See self-service running on your own data.

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

Book the 30-min kickoff Ask us anything