EU-native Identity Governance & Administration · built in BelgiumEU-native IGA · built in BelgiumCustomer-first · grounded in the running product

How RapidValue works

Three loops do the work.
One inbox asks you to decide.

The menu follows the order in which you get value: Connect, See, Govern, Prove. Underneath, three loops keep running. A data check decides what RapidValue is allowed to report, and one inbox collects everything a person has to decide.

The model

Each loop runs at its own pace, and decisions arrive in one inbox

The data loop and the access loop run all the time, at the speed of your systems. The model loop moves at the speed of the people who own roles and applications. Whenever a loop needs a person to decide, the question goes to the same inbox.

Runs all the time

The data loop

Is what we know good enough to act on?

RapidValue reads what is in your systems. For each account it works out whose it is, what kind of identity it represents and who answers for it. Anything it cannot work out is listed as a gap for someone to resolve, and RapidValue does not guess.

The data checkOnly claims we can back up pass

Where it lives in RapidValue
Systems & connectorsData model & authorityNon-human identities

Runs at human pace

The model loop

What exists to be governed, and should it still exist?

Applications, entitlements and roles are proposed, shaped, given an owner, formalised and eventually retired. These decisions can stay in place for years, so people take them at their own pace.

Where it lives in RapidValue
Applications & entitlementsRoles & role mining

Runs all the time

The access loop

Who should have which access, and is that still right?

RapidValue compares the access people should have with what the target systems show. Approvals, lifecycle events, reviews and reconciliation close the difference, and the reason for each change is kept.

Where it lives in RapidValue
Identity lifecycleRequests & approvalsAccess policiesReconciliationAccess reviewsSegregation of duties
One governed inboxWhere people decide
Data gapOwner missing for a privileged accountAssign owner
Role proposalFinance role is ready for owner reviewReview model
Access decisionContractor access reaches its end dateDecide access

Every decision returns to its loop with the reason attached.

The data check

RapidValue only reports what the data supports

Checking data quality does not stop after onboarding. It keeps running, and when RapidValue does not know something it says so.

No activity datais reported as untracked.

If RapidValue cannot read activity, an empty last-used date is shown as untracked. The account is not counted as dormant.

No review scheduleis reported as a gap.

A rule that only reacts to events is listed as a review gap. It is not counted as a scheduled review.

Nothing to measureis left out of the score.

A control with nothing to measure is excluded. It is not rounded to 0% or 100%.

One inbox

Decisions that need a person arrive in one inbox

Approvals, certifications, reconciliation differences and findings arrive in the same list. Each item says which loop asked, why it matters and where your decision goes.

  • When a question is answered, it leaves the list and the reason is kept on the trail.
  • A few decisions have their own screen, such as releasing a held batch of changes and reviewing emergency access afterwards.
  • The navigation badge and the home tile show the same count from the same source.

The same model, hour by hour

The first morning starts all three loops, and you keep what you set up

  1. ScopeWe agree on the question, the boundary and a safe starting mode.
  2. Connect HRHR becomes the source for people before we match any accounts.
  3. Connect one applicationWe read accounts, grants and the data the check needs.
  4. InspectEach gap becomes a task with a name and an owner.
  5. DecideYou leave with a first view and a clear next step.

See the loops in the product

Walk through the real product screens

Try a scenario