Modules and interfaces
Modules and interfaces
Section titled “Modules and interfaces”RegulaLink is not a single app: it is an organization workspace (your tenant) where several interfaces and modules combine. Modules open with your plan (and sometimes self-regulator mode). Account permissions then decide what you see.
This page is the business map. Pillar detail: Collect, Authorizations, Regulation, Intelligence, GRC.
Five interfaces
Section titled “Five interfaces”1. Admin console
Section titled “1. Admin console”Who: agents, instructors, compliance leads, administrators, leadership.
Role: configure (forms, workflows, catalogues), instruct (files, complaints, licences, findings), oversee (GRC, analytics, reports).
Typical menus: Collect · Licences · Regulation · GRC · Reports · Analytics · Settings / accounts.
2. Operator workspace (Entity)
Section titled “2. Operator workspace (Entity)”Who: the entity, member, subsidiary or partner you oversee.
Role: complete identity, file an authorization request, meet obligations (“My compliance”), contribute to GRC when assigned a risk / audit / assessment, message on a licence case, optionally pay an invoice.
Operators do not configure framework studio or sanction catalogues: they execute what concerns them.
3. Public portal
Section titled “3. Public portal”Who: citizens, third parties, applicants, partners.
Role: browse the verifiable registry, verify a QR proof, file a complaint, sometimes report a finding, start KYC onboarding, read published indicators if you expose them.
4. Guided KYC (PWA)
Section titled “4. Guided KYC (PWA)”Who: the applicant, or an agent assisting them.
Role: step-by-step identity form tied to a category (actor type). Same form engine the admin builds for Collect.
5. Field app (Collector)
Section titled “5. Field app (Collector)”Who: agents on mission.
Role: sessions / missions, offline capture, sync, findings depending on modules. Product maturity is still evolving.
How a module opens
Section titled “How a module opens”| Lever | Effect |
|---|---|
| Plan | Enables a module list (Essential → Enterprise) |
| Organization mode | Regulator vs self-regulator (labels + GRC auto on self-regulator) |
| Permissions / roles | Refine what your account sees inside an active module |
| Add-ons | e.g. ISO 27001 pack on top of GRC |
Menu labels are not the source of truth — enabled modules are. Example: complaints ship in Essential, but the admin menu often nests them under “Licences”.
Module overview
Section titled “Module overview”| Group | Modules (keys) | Typical entry plan |
|---|---|---|
| Collect & identity | Actors (providers), complaints, migration, membership invoicing | Essential (+ invoicing on Professional) |
| Authorizations | Licences, obligations | Professional |
| Regulation | Infractions, sanctions, business rules, regulatory reports | Professional |
| Oversight | Analytics (baseline from Essential) | Essential → extended on Intelligence+ / Enterprise |
| GRC | GRC, risks, audits | Enterprise or self-regulator at first-run |
Intelligence+: at technical bootstrap, the same module list as Professional — difference is mostly volumes and progressive analysis / copilot rollout.
Collect & identity
Section titled “Collect & identity”Actors / operators (providers)
Section titled “Actors / operators (providers)”Purpose: build and maintain the identity base (KYC / KYB) of actors you follow.
In admin: categories (types + forms), identity files, field sessions, operator directory.
Typical journey:
- Create a category (e.g. “Provider”, “Member”, “Agent”) and its form.
- Open the KYC link, public portal, or a Collector mission.
- Instruct the file (documents, validations, statuses).
- Publish / expose the registry and QR proof.
Regulator: external operators. Self-regulator: members, agents, partners — same engine.
→ Detail: Collect pillar.
Complaints (complaints)
Section titled “Complaints (complaints)”Purpose: receive and instruct reports / disputes (citizen, third party, sometimes operator).
Where: forms + workflows in admin; filing often on the public portal; instruction under the Licences menu (even without the licences module).
Common chain: filing → instruction → resolution → optional linked sanction.
Migration (migration)
Section titled “Migration (migration)”Purpose: import an existing stock (CSV) instead of retyping everything.
Membership / commission invoicing (invoices)
Section titled “Membership / commission invoicing (invoices)”Purpose: bill membership, commissions or fees tied to Collect / licences (when configured). Typically Professional+.
Authorizations & obligations
Section titled “Authorizations & obligations”Licences (licences)
Section titled “Licences (licences)”Purpose: issue and follow authorizations (approvals, internal clearances, permits).
In admin: types, sectors, multi-level SLA workflows, subprocesses, messaging, cases.
On Entity: application, documents, stage tracking, dialogue with authority / HQ.
Self-regulator: same tool for internal clearances (not necessarily a public approval).
Obligations / compliance
Section titled “Obligations / compliance”Purpose: calendar of duties and evidence (periodic filings, documents) tied to a licence or HQ.
On Entity: My compliance — see what is due, upload evidence, track status.
Regulation
Section titled “Regulation”Infractions
Section titled “Infractions”Purpose: formalize a finding (inspection, report, complaint follow-up) with types and PV workflows (draft → validation → execution as configured).
Sanctions
Section titled “Sanctions”Purpose: apply a measure from the catalogue (warning, fine, suspension, internal corrective measure) from an infraction, a complaint, or directly per rights.
Business rules (regulatory_rules)
Section titled “Business rules (regulatory_rules)”Purpose: versioned schedules and automations (thresholds, chains) to reduce one-off handling.
Regulatory reports (reporting)
Section titled “Regulatory reports (reporting)”Purpose: campaigns and forms for periodic submissions (same form builder as Collect / complaints).
Shared form builder
Section titled “Shared form builder”One builder serves three families:
| Family | Use |
|---|---|
| Identity (KYC/KYB) | Actor categories, PWA, Collector |
| Complaints | Report forms |
| Regulatory reports | Periodic declarations |
Steps, fields, object lists (object_array), calculations and conditions: same logic. See Collect — form builder.
Oversight & Intelligence
Section titled “Oversight & Intelligence”Analytics (baseline)
Section titled “Analytics (baseline)”From Essential: volume cockpit, queues, first indicators.
Beyond: indicator studio, preparation pipelines, optional public publication.
Réglia and executive cockpits
Section titled “Réglia and executive cockpits”Conversational copilot and advanced cockpits: progressive rollout, tenant configuration dependent (e.g. LLM). Do not expect magic without activation.
GRC, risks, audits
Section titled “GRC, risks, audits”Purpose: comply and prove risk mastery — internal policies, national / regional frameworks, international standards (ISO 31000 included; ISO 27001 add-on).
| Module | What you do |
|---|---|
| GRC | Frameworks, cockpit, “To do” inbox, assessments |
| Risks | Register, appetite, treatments, owners |
| Audits | Plans, findings, checklists, evidence |
Commercial catalogue: Enterprise. Self-regulator mode: typically enabled at first-run.
→ GRC and internal compliance.
Where it appears in admin
Section titled “Where it appears in admin”| Menu group | Frequent topics |
|---|---|
| Collect | Operators, files, sessions, categories, migration, (invoices) |
| Licences | Licence cases, workflows, messaging, obligations, complaints |
| Regulation | Infractions, sanctions, rules |
| Reports | Types, forms, submissions |
| GRC | Cockpit, frameworks, risks, assessments, audits |
| Analytics | Cockpit, indicators, pipelines |
End-to-end journeys (summary)
Section titled “End-to-end journeys (summary)”| Intent | Modules | Interfaces |
|---|---|---|
| Register and publish a park | Collect, complaints | Admin + KYC / public / collector |
| Authorize then follow over time | Licences + obligations | Admin + Entity |
| Control and sanction | Infractions, sanctions, rules | Admin (+ public / field) |
| Collect periodic filings | Reports | Admin + Entity |
| Prove internal compliance | GRC, risks, audits, obligations | Admin + Entity |
| Steer | Analytics (± Réglia) | Admin (± public if published) |
Product cycle: register → authorize → control → comply / steer.
Known limits
Section titled “Known limits”- Intelligence+ ≠ extra bootstrap modules vs Professional.
- Collector maturity still evolving.
- Réglia needs activation / config.
- Official gazette / advanced DMS: not the current core.
- Live federation between regulators: not the current path.
- Some screens still sound “regulator” in self-regulator mode.