How RapidValue works

Every access shows who owns it, why it exists and what happened since.

RapidValue reads your HR system and your applications, and puts the evidence next to every right. You decide with the facts on screen, and the decision goes on the trail.

1 morningHR and one application, gaps on screen by lunch
~15 minper standard connector
30 daysfree pilot, read only
OwnerReasonSystem
The same trail draws the R in our logo. Fictional demo data
Reads from your
HR systemActive DirectoryMicrosoft Entra IDSCIMLDAPREST
The explained decision

One screen answers the auditor’s question.

This is the Inbox with one decision open. The owner is asked to confirm an access, and the reason for the question and the decision trail sit next to it.

The Inbox of RapidValue: an access request that the manager decides, with the reason for the question and the person’s HR data
The Inbox: one decision, with its owner, its reason and its trail.
Owner

The person who answers for the access, for example the owner of an application.

Reason

The role or rule that gave it, and whether that reason is still true today.

Trail

Who granted it and when, what HR reported since, and what RapidValue found.

Joiners, movers and leavers follow HR.

Your HR system says who works here and in which role. When that changes, RapidValue compares what the person should have with what your systems show.

  1. AddedRead invoices, from the rule for accounts payable

    Someone joins

    Access a rule grants from HR data is added automatically, within the writes you enabled.

  2. To decideSofie Maes, from Finance to Sales

    Someone moves

    What no longer fits the new role lands in front of the right person, with the reason attached.

  3. RemovePieter Claes, left 14 Oct

    Someone leaves

    The access of leavers is removed. What is still open shows up as a gap with a name next to it.

Examples from the fictional Northwind Logistics. Fictional demo data

What keeps it running

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

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.

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.

One governed inboxWhere people decide
Three independent loops · feed one governed inbox
  • 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.

Reviews, requests and new systems, in the product.

Three places where the evidence does the work. Pick one to see it.

Every line explains itself.

All reviews in one place, with their progress and deadline. Inside a review, each line shows the person, the access, the reason and, where the system reports it, when the account last signed in, with a suggestion to keep or remove. Leavers are flagged, so they are not approved by habit.

When RapidValue cannot read activity, it shows it as untracked and does not count the account as dormant.

Access reviews in RapidValue: progress per review, open items and deadlines
Access reviews: progress per review.
connecting systems

One place that reads all your systems.

A standard SCIM, LDAP/AD or REST system takes about 15 minutes with the wizard. For a complex system without a standard interface, we build the connector as a service in 3 to 5 days.

Source of people

HR system
RapidValueOwner, reason and trail for every access

Directories

Active Directory
File server
Microsoft Entra ID
Fleet planning
Applications that get their access through directory groups

Applications with their own connector

Finance ERP
Standard interfaces, about 15 minutes
SCIMLDAPREST

Complex systems

Connector built as a service, 3 to 5 days

You choose per connector whether it runs directly from our platform or through an agent in your network. In agent mode, the credentials stay in your network. Example systems from the fictional Northwind Logistics.

the audit trail
Every grant, change and decision stays on the trail, with who did it, when and why.

When the auditor asks about one line, you open it and read the answer. Audit history is hash-chained, and signed exports make tampering detectable.

  1. 3 MarGranted by An Janssens, Pieter’s manager
  2. 3 MarThrough role FIN-AP-APPROVER
  3. 3 MarFinance ERP · Approver
  4. 14 OctHR system: Pieter Claes left Northwind Logistics
  5. 30 OctFound on the first morning: account still active
  6. 30 OctRemove access sent to Tom Claes, application owner
Fictional demo dataThe trail reads in the same order as our logo: owner, reason, system.

You see it on your own data in one morning.

Serge, the founder, runs the first morning with you. From 09:00 to lunch, your HR system and one application are connected and the gaps are on screen.

  1. 09:00

    Scope

    We agree on the question and where to start.

  2. 09:30

    Connect HR

    Your HR system becomes the source for people.

  3. 10:15

    Connect one application

    Accounts and rights come in from the first target system.

  4. 11:00

    Inspect

    Each gap on screen, with a name next to it.

  5. 11:45

    Decide

    You leave with a first view and a clear next step.

Want the morning to go to your data? Arrange the access beforehand: Before 09:00.

The week after, the proof of concept takes about one week on your own data.

Bring one access question to a first morning.

The 30-day pilot is free and read only, on your HR source and one target system. We run two pilots at a time.