Understanding a collection connection
01What a connection allows #sec_d8b8641f
A connection links REVIEWIT to an instance of a solution: a Microsoft 365 tenant, a Google Workspace organization, a Slack workspace, a GitHub organization. It serves to collect, read-only, the accesses that your campaigns will have reviewed.
A connection does not collect "all or nothing". For each resource of the solution — SharePoint sites, shared drives, groups, repositories — REVIEWIT states whether it is collectible, and if not, what is missing. This is the resource's verdict.
A resource that the connection cannot collect remains importable by mapping: the manual path never depends on the connection's verdict.
02The words on the screen #sec_5f452fe1
| Term | What it refers to |
|---|---|
| Connection | The link with a solution instance. It is suspended and reactivated by an administrator's action, never by itself. |
| Identifier | The application or service account by which REVIEWIT authenticates. A connection can carry several: a read-only collection identity, a narrow remediation identity. |
| Resource | What is collected: a type of object from the solution. Each resource has its own requirements. |
| Right | A permission granted to the identifier at the provider: application role, scope, directory role. |
| Administration condition | A setting that is not a token right: a tenant setting, a role group, a management application, a role on a subscription. REVIEWIT observes it through a real read-only call. |
| Proof | What REVIEWIT has observed and dated: the rights of the token obtained, the roles, the conditions, the service's reachability. Proof ages: rights are valid for 24 hours, authentication for 48 hours. |
| Verdict | What the connection allows for a resource, calculated from the proofs and published requirements. |
03Where the verdict comes from #sec_9067d872
For each resource, REVIEWIT publishes a contract: the list of rights and conditions that make it collectible. A contract often says "one of the following options is required": several different rights unlock the same resource, and a single one is sufficient. REVIEWIT never asks for the broadest when a narrower one covers the need.
"Check rights" queries the provider, for each identifier: what rights the obtained token carries, what roles, what conditions are met. The verdict is then recalculated each time the record is opened, without a new call to the provider. The check is automatically redone every 24 hours.
The token is never stored: only the observed facts are.
04One connection, multiple readings #sec_54dca6a4
A connection record can be read in four ways:
- By resource — what is collectible, by which identifier, and if not, each way to remedy it;
- By identity — what an identifier opens, what it does not open, and the rights it holds without any selected resource using them;
- By right — what each granted right is used for; a right that is not used is labeled unused;
- What needs to be granted — the minimal list to give to your administrator, identity by identity, with a script for them to execute themselves.
REVIEWIT never grants a right: it states which one, your administrator grants it at the provider, and the next check observes it.
05To go further #sec_364d211b
- Prepare a Microsoft 365, Entra ID, and Azure identifier
- Prepare a Google Workspace identifier
- Prepare an identifier for a token-based solution
- Read a verdict
- Rights reference by resource