External identity management
Every external person has a sponsor, and their access and end date are decided at the start.
A sponsor invites someone, or the external person sends a request. Before any access is proposed, RapidValue records who they are, where they come from, why they are here and until when. Reminders, extensions and offboarding stay linked to that person and their sponsor.
What you get
Access proposed from why they are here
An end date from the start
Access removed and checked when it ends
It works in three steps
Each step records its reason, and the next step uses it.
Intake & qualify
A sponsor invitation or an external request starts the flow. RapidValue then collects the identity type, organisation, purpose, required profile data and validity period.
Decide & activate
RapidValue proposes access from the purpose and context, sends it to the right approvers and activates only the grants they approved.
Renew or close
The sponsor gets a reminder before the end date. Without an extension the person is offboarded automatically, and RapidValue checks the removal in every connected system.
However an external person arrives, they land in the same place
A supplier’s engineer is needed by Monday, a partner has its own administrator, or a roster arrives as a spreadsheet. All of these are reasonable requests, and all six routes below end the same way: the person gets an identity with the status pending and an open onboarding case, and holds no access yet.
What every route has in common
- The person exists, but holds no access before activation
- Matching access is held back and shown as waiting
- Only allowed fields are collected, others are refused
- A synchronisation or an import can never activate anyone
Nobody gets access before a person says so
The lock sits in the access calculation
Every provisioning decision uses that calculation, so no screen, import or synchronisation can go around it.
A checklist before activation
The onboarding profile lists what has to happen first, such as the data to collect and the documents to receive. An administrator can waive a step only with a written reason, and the waiver is logged as a warning.
One explicit activation
Activation is a separate act by an administrator. It refuses while a required step is open and names which one. After it, reconciliation grants the access.
Rejecting closes the case
Rejecting needs a reason. It ends the identity and withdraws the open tasks. A case that goes quiet expires after 90 days by default.
RapidValue stores the documents and puts them in front of a person. It does not check what is in them and does not verify identity documents. No screening provider is connected today.
The sponsor and the end date are there from the start
A sponsor for every person
The sponsor is recorded as the owner. When the sponsor leaves, the same handover applies as for any other owner.
Your dates win
End dates are enforced whatever the partner’s system reports. After the end date and a grace period the identity is ended and the access is removed.
Warnings and renewal
The sponsor is warned two weeks and one week before by default. Renewing extends the contract end of the organisation and the end date of every person at once.
Data that ages out
Each collected field says when it is erased: at contract end, or a number of days after intake or activation. The audit record names the fields that were erased and never their values.
You have no HR department that marks externals as leavers. The end date does that job.
External access always has an end date, even though no HR event exists to end it.
Included in every price
There is no module to buy for this. The price depends only on how many identities you govern.