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

Upload documents

A fresh applicant lands on the upload page, which lists the documents the intake requires. They can drop a whole folder or single files. Each upload is automatically classified, for example "Trade Licence" or "Passport", and its key fields are read. The applicant then chooses to apply the documents to their application, which fills the form once every document has been read, or to fill the form in manually. See Documents and AI extraction.
3

Complete the form

A multi-page questionnaire with inline validation and per-section progress. A value the documents filled carries an AI Filled tag until the applicant edits it; an answer they typed themselves is never overwritten. Validation is enforced at submission, so a malformed email address or date cannot be submitted.
4

Map ownership

For corporate applicants, a visual builder captures the beneficial-ownership tree with share percentages. The builder shows the running total of direct shareholdings, and a total above 100 percent blocks submission. Any ownership issue that remains is flagged to your compliance team on the case.
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, and the form closes.

After submission

The applicant can check their status at any time, and is emailed when the outcome changes: approved, rejected, a request for more information, or an answered item sent back for another round.

An information request carries a cover note from your team and lists exactly what is needed. Each item is one of three kinds: a question, a correction to a specific answer, or a document. The applicant answers every item in place in the portal's Requests tab and submits the round in one action. Your team then accepts each answer or sends the item back, which opens another round. The rest of the application stays exactly as submitted.

Applicants have no password
Applicants and teammates sign in only through a time-limited, single-use link, which lives three days. If a link lapses, a fresh one can be issued by your team from the dashboard or by your systems through the API, and the applicant or a teammate can request one themselves from the portal's sign-in page by entering their email. See Integration guide for how the link fits an integration.

What the applicant cannot do

  • Change their own status. Status is set only by the platform. See Onboarding lifecycle.
  • Edit the form after submission. Every later change goes through an information request, item by item, when your team asks for it.
  • 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.