Onboarding

/onboarding is the first stop for a new end user, who has no organization until they create one or are invited into one. Signed-out visitors are sent to /login.

What you enter#

A business name and a type: customer ("apply for credit") or supplier ("receive applications"). The form posts to POST /v1/account/organization and then continues to /post-login.

What happens#

• The person becomes the organization's owner: a supplier becomes ORG_ADMIN; a customer becomes APPLICANT with the customer administrator permission set.
• A supplier organization is created as pending approval, an empty application configuration is created, and a vendor-approval request email is queued for platform staff (see Staff onboarding a vendor). A time-boxed automatic approval window can approve it at once if the owner opened one.
• The audit event org.created is written in the same transaction.

After you create it#

A customer's dashboard shows "Finish setting up" as a task list (every task with its status, any order, gone when done) and, while applying is blocked, a notice that says why and what can still be done; a supplier's dashboard shows the compact card. See Onboarding steps and gates. Organizations created here are gated: some actions wait for a step.

Errors#

• 403: staff and support (impersonation) sessions cannot create a business.
• 400: missing name or type. 409: the account already belongs to a business, or a supplier name matches an existing business ("ask its administrator for an invitation"). 429: more than 5 attempts per hour.

A company name never joins anyone to somebody else's account. Joining requires an invitation to the email address you sign in with.

Related#

• Team and permissions