Synchronizing
Architectural Primitives

The applicant portal

The applicant receives a secure link and lands in a guided flow. They never create an account, and they never choose a password. Everything they need to do is sequenced for them.

The applicant journey

1

Consent

They review and accept a data-processing consent before any upload. The acceptance is recorded with its timestamp.
2

Complete the form

A multi-page questionnaire with inline validation and per-section progress. Validation is enforced at submission, so a malformed email address or date cannot be submitted.
3

Upload documents

Each upload is automatically classified, for example "Trade Licence" or "Passport", and its key fields are extracted to pre-fill the form. The applicant reviews and accepts each proposed value rather than having it silently applied. See Documents and AI extraction.
4

Map ownership

For corporate applicants, a visual builder captures the beneficial-ownership tree with share percentages, validated so the shares reconcile.
5

Invite teammates (optional)

The owner can invite colleagues to help complete the form. Teammates can edit and upload; only the owner can submit.
6

Submit

Once the form is complete and valid, the owner submits. The application enters your analyst queue at Pending.

After submission

The applicant can check their status at any time, and is emailed when the outcome changes: approved, rejected, or a request for more information.

An information request lists exactly what needs fixing and reopens only the relevant sections so they can resubmit. The rest of their application stays as they left it.

Applicants have no password
Applicants and teammates sign in only through a secure single-use link. If a link lapses, a fresh one can always be issued, and teammates can request their own replacement link from the portal without staff involvement. See Integration guide for how link expiry shapes an integration.

What the applicant cannot do

  • Change their own status. Status is set only by your team's decision actions. See Onboarding lifecycle.
  • Edit sections that are not open to them. After submission, only the sections an analyst reopens become editable again.
  • Submit as a teammate. Teammates contribute answers and documents; only the owner submits.
  • See another application. Each applicant identity is scoped to its own application within one tenant.