RapidValueDocs RapidValue.eu
Docs/Architecture & trust

What you see and why

There is one source of truth: the platform's database. The interface holds no business data of its own; it asks the server for every screen. But what a screen shows is not the whole database. The server decides, for each request, which screens you may open, which people you may see and which of their fields, and the platform keeps a good deal more than any screen shows.

A request passes four server-side filters in order: the audience gate answers 403, the subject scope answers 404, the manager reach narrows a manager's team, and field visibility hides or masks fields. What remains reaches the interface.

Three ways in, one database

Client How it authenticates What it reaches
The web interface A person's session after sign-in The product API, filtered for that person
The machine API An API credential with scopes A separate gateway with a smaller set of endpoints. See API reference
The MCP server OAuth on behalf of a person or an agent Governed tools, decided per call. See Governing AI agents

All three read the same data through the same services and the same tenant boundary (Tenant isolation), and each is checked on the server: a person by the four filters below, a machine credential by its scopes, and an MCP call by the decision taken on that call.

What the platform holds that no screen shows

  • The raw source record behind each account, kept for drift detection and provenance.
  • The evidence of every run: sync and reconciliation snapshots and logs.
  • The audit chain and the configuration change log. See Evidence and signing.
  • Secrets. Connector credentials are stored in the vault and never returned to the browser. With the tier-3 agent they never reach the control plane at all. The identities and accounts that sync reads do live in the control plane in every mode.

Values that depend on other data, such as a person's status, lifecycle stage or the label of their department, are computed by the server when you ask, so the interface never holds a stale copy of a rule.

The four filters

1. Audience: is this screen for you?

Screens and writes are gated on capabilities from one permission matrix, not on hand-written lists of role names. If the screen is not for you, the answer is 403. The menu you see is built from the same capabilities, but it is only a hint: hiding a menu item is not the control, the server is.

The menu has two spaces, Work and Setup, with a switch under the brand and a Setup button in the top bar, and related pages fold under one expandable row. End users and access reviewers get one short list instead (Home, Inbox, Request, My requests, My access, Access reviews), with no spaces and no Setup button. Each item still shows only when its own capability allows it.

2. Subject scope: may you see this person?

Within a screen you may open, the server checks each person you ask for. You see a person when at least one of these holds:

  • it is you;
  • they are in your team as a manager;
  • a decision about them is waiting for you;
  • your role oversees the tenant, such as administrators, auditors and the security team.

If none holds, the answer is 404, exactly as if the person did not exist. A 403 would confirm that they do. Lists apply the same rule as the detail page, so you cannot open someone the list would never show you. One known gap the other way: a few roles that may open any person (HR, risk, compliance, legal and break-glass) still see only themselves in the identity list, global search and org chart. The joiner, mover and leaver views follow the same scope: a manager sees the lifecycle events of their own team, not the tenant's.

Owning something is not a reason to see the person. The owner of a system or an entitlement reads the holders' access on what they own: the holder's account on that system and, in an access breakdown, only the grants on what they own. The holder's profile answers 404 to an owner, as it would to anyone else outside the four reasons above. Holder lists name a holder you may not open instead of linking to a profile that would answer 404. The owner of a system lists every account on that system and reads the writes that wait for review on it; releasing them stays with whoever configures the system's writes. Risk, access at a past date and effective permissions cannot be split per grant, so they stay closed to an owner.

3. Manager reach: how far down a manager sees

How far a manager's team reaches is a tenant setting: direct reports (the default, for data minimisation) or the whole reporting line. A person with two contracts is in the team of each manager who manages one of them; see Employments and multi-affiliation. The identity list says which reach it uses, and each row says why it is visible.

A manager's identity list set to the whole reporting line. One row carries a Reporting line chip: that person reports to one of the manager's direct reports.
A manager's list with the whole reporting line switched on. The chip says why a person who is not a direct report is visible.

Seeing is not deciding. Who approves is decided by the approval step, not by who can see the person.

4. Field visibility: which fields of that person

An administrator sets, per role and per field, whether the field is hidden, read or write, with overrides per identity type. A field's sensitivity (public, internal, sensitive or personal data) sets its default. Where a person holds several roles, the most permissive level wins.

The field visibility matrix for identities: one row per field, one column per role, and for each a choice of hidden, read or write.
The field visibility matrix: hidden (H), read (R) or write (W) per field and per role.
  • Writes are checked on the server: a role cannot change a field it may only read.
  • Reports and exports remove a hidden column from the file, not only from the screen. See Reporting.
  • The identity record itself is masked on the server: the detail and list reads, the responses to a create or an edit, the org chart and global search leave a hidden field out, together with what can be derived from it (a hidden manager also hides the manager's name), and name the masked fields in the response. The list cannot be searched, sorted or filtered on a hidden field: a filter on one returns an empty page.
  • Manager reviews, reconciliation views, the access explorer and the Contexts over time card mask hidden fields on the server as well.

The org chart and global search also follow the subject scope of step 2: they show only the people the reader's Identities list shows, and the org chart's counts include only those people.

Did this answer your question?One click records the page; add detail by email if something is missing.

Try “tenant isolation”, “role mining” or “Entra”.