Skip to content

Why features are locked until onboarding finishes

What the wall blocks

A new client workspace cannot do raise-affecting things until a human reviewer activates it. Blocked actions are inviting an investor, opening a signing envelope, sending a signing invitation, and any offering change.

Reading, exploring and preparing are not blocked. The wall sits on the actions that affect a raise.

The rule, exactly

The workspace status must be exactly active. Anything else is blocked, including a brand new workspace with no status yet, onboarding, pending_kyb, suspended, offboarding and closed.

This is deliberately an allow list rather than a list of bad states. If the system does not recognise a status, it blocks. Activation is a decision someone made, never a default a half-onboarded workspace falls into.

Where the refusal actually happens

The card you see in the app is a convenience. The real refusal is server side, inside each mutating endpoint, which re-reads the status itself and fails closed if it cannot read it. Nothing you can change in the browser lets an action through.

What the checklist covers

/app/issuer/onboarding collects the KYB material: entity details, ownership and beneficial owners, supporting documents, and a compliance questionnaire. The signatory verification card lives on the same page.

Completing the checklist is not approval

Finishing every item does not unlock anything by itself. A reviewer activates the workspace. Completeness and approval are two different things and the app never presents the first as the second.

Who can see the onboarding surface

Questionnaire submissions carry declarations about named individuals, so reading them is restricted to owners and admins. A plain member is shown that the surface is restricted rather than an empty checklist, because an empty list would be a lie.

When a read fails

Each part of the onboarding status is one of three things: ready, unavailable in this environment, or failed. A failed read renders as "we could not check", never as "you have submitted nothing". Telling someone they filed nothing when the read broke would invite them to re-file compliance declarations about named people for no reason.