Authorizations pillar
Authorizations
Section titled “Authorizations”Authorizations turns a known identity (Collect) into a right to operate followed over time: issuance, renewal, conditions, evidence.
Entry plan: Professional (PREMIUM) — licences (+ often invoices). Obligations ride this cycle (and remain useful for self-regulators even without a public approval).
What this pillar covers
Section titled “What this pillar covers”| Capability | Where it lives | Notes |
|---|---|---|
| Licence types | Admin → Licences → Types | Each type has its journey and documents |
| Sectors / scopes | Admin → Sectors | Group clearances |
| Multi-level workflows | Admin → Workflows | Stages, roles, SLA |
| Subprocesses | Admin | Branches (visit, complement, committee…) |
| Authorization cases | Admin → Cases ; Entity | HQ instruction ↔ operator filing |
| Messaging | On the case | Formal dialogue HQ ↔ operator |
| Obligations | Admin + Entity My compliance | Calendar and evidence after (or without) a licence |
| Related invoicing | If invoices | Instruction / membership fees when configured |
Applications involved
Section titled “Applications involved”Configure the catalogue (types, sectors), workflows, instruct cases, set obligations, message, decide (grant, defer, refuse, renew).
Entity (operator)
Section titled “Entity (operator)”- Start from a known identity (or complete it).
- File an application on a licence type.
- Follow stages and answer document requests.
- Once authorized: meet My compliance (deadlines, evidence uploads).
Public / KYC
Section titled “Public / KYC”The public does not issue licences; it can verify the actor via the Collect registry if you publish status.
Typical Professional flow
Section titled “Typical Professional flow”- Define authorization types and workflows (who validates what, in how many days).
- Operator files from Entity (or an agent opens the case).
- Multi-stage instruction + messaging.
- Decision → optional registry publication.
- Open periodic obligations (filings, evidence, controls).
- Renewal / change / suspension as events unfold (including regulation follow-up).
Obligations: ongoing compliance
Section titled “Obligations: ongoing compliance”Getting an authorization is not the end of the cycle. Obligations let you:
- surface deadlines (Entity sees the calendar);
- collect evidence (documents, reports);
- feed oversight and, for self-regulators, link to GRC.
In self-regulator mode you can use HQ obligations even without an external licence catalogue: that is internal compliance for members / sites.
REGULATOR vs SELF_REGULATOR
Section titled “REGULATOR vs SELF_REGULATOR”| Mode | Authorizations reading |
|---|---|
| REGULATOR | Public approvals / permits toward external operators |
| SELF_REGULATOR | Internal clearances, rights to operate in the network, member compliance |
Same screens; intent and labels adapt.
Limits
Section titled “Limits”- Not on Essential (except complaints, which sit under the Licences menu without being licences).
- Official gazette / advanced DMS: not the current core.
- Without the licences module, GRC and Collect remain usable (especially self-regulator).
- Modules and interfaces
- Regulation — findings and sanctions after control
- GRC and internal compliance
- Plans