Collect pillar

Collect

Collect is RegulaLink’s entry pillar: build the identity base of actors (operators, members, partners…), keep it current, make it publicly verifiable, and open complaint / migration channels.

Entry plan: Essential (STANDARD) — modules providers, analytics, complaints, migration.

What Collect actually covers

Capability	Where	Notes
Categories / actor types	Admin → Collect → Categories	Each type has a form (form builder)
Identity / KYC dossiers	Admin; KYC PWA; Entity	Submissions, documents, statuses
Field sessions	Admin → Sessions; Collector mobile	Offline collect + sync
Public registry & QR	Public	Citizen / third-party verification
Complaints	Admin (Licences UI group) + Public	complaints on Essential — admin menu often under Licences rail
CSV migration	Admin → Migration	Import existing stock

UI vs plan

On Essential, complaints are included even if the admin sidebar nests them under “Licences”. Gating is by module, not menu label.

Form builder

Schemas are built in admin (FormSchemaBuilder) — also reused for complaints and regulatory reports.

Object lists (object_array): repeatable rows (directors, staff, equipment…) with per-subfield config (list source, computed fields, visibility, validation) via modal.

Typical Essential flow

1. Create a category + form.
2. Publish KYC link or open field collection.
3. Instruct dossiers in admin.
4. Expose public registry + QR.
5. Configure complaint forms if the citizen channel is open.
6. Optional CSV migration.

REGULATOR vs SELF_REGULATOR

Mode	Collect reading
REGULATOR	External operators to register / publish
SELF_REGULATOR	Members, agents, internal partners — same engine, adapted labels / first-run

Essential limits

No licences, infractions/sanctions/rules, or GRC (Enterprise; SELF_REGULATOR may unlock GRC at first-run). Analytics is baseline; Réglia / pipelines = Intelligence+ / Enterprise (progressive).

Next

• Modules and interfaces — full module map
• Authorizations
• Plans
• First-run