Set up your organisation

On this page

The four steps
A. Who you are
B. Organisation
C. First entity
D. Review and file
How slugs are chosen
What filing actually creates
Limits
Things worth knowing

The setup wizard runs once, when you first sign in without an organisation. It collects who you are, your organisation, and your first entity, then files all three in one go.

The four steps#

Progress is saved to your browser as you type, so closing the tab does not lose your work. Each step shows a live count of the fields still required, and Continue stays disabled until that count reaches zero.

A. Who you are#

Fields collected in step A
Field	Required	Notes
Role	Yes	One of eight: chief executive or founder, general counsel or legal, compliance officer, chief risk officer or risk lead, internal audit, board or corporate secretary, COO or operations, other.
Full name	Yes	Prefilled from your account.
Direct phone	No	Stored on the organisation profile.

B. Organisation#

Fields collected in step B
Field	Required	Notes
Legal name	Yes	The registered entity name.
Display name	No	Defaults to the legal name.
URL slug	Yes	Becomes the first segment of every in-app URL.
Country of registration	Yes
Industry sector	Yes	Twelve options spanning finance, banking, health, technology, manufacturing, engineering, retail, real estate, professional services, education, public sector and other.
Headcount	Yes	Six bands: 1 to 10, 11 to 50, 51 to 200, 201 to 1k, 1k to 5k, 5k and above.

C. First entity#

An entity is the unit that owns connectors and a ledger. Most organisations start with a headquarters and add more later.

Fields collected in step C
Field	Required	Notes
Entity name	Yes
URL slug	Yes	Second segment of in-app URLs.
City	No
State or region	No
Operating country	Yes	Defaults to the organisation's country. Override it if this entity operates elsewhere.
Entity type	Yes	Headquarters, branch or city office, department or function, business unit, or project or engagement.
Primary use case	Yes	Board governance, compliance and regulatory, risk management, internal audit, or vendor and third-party.

D. Review and file#

The last step has no fields of its own. It shows everything you entered with Edit links back to each step, and you can only jump back to a step you have already completed.

How slugs are chosen#

Slugs are derived from the name as you type it: lowercased, with runs of non-alphanumeric characters collapsed to single hyphens, truncated to thirty characters. The moment you edit the slug field yourself, it stops following the name, so your edit is never overwritten.

The rules are the same on both sides of the wizard and are enforced again on the server: lowercase letters, digits and hyphens only, three to thirty characters, and no leading or trailing hyphen. A set of reserved words is rejected. Full details are in Slug rules and reserved names.

What filing actually creates#

Filing runs four visible phases: creating the organisation, provisioning the first entity, removing the default scaffold, and finalising your account. The third phase exists because creating an organisation automatically produces a default entity with a generated name; the wizard deletes it so you are left with exactly the entity you named.

Your answers from step A and step B are stored as profile metadata on the organisation. Editing the organisation later from settings updates that metadata in place and preserves the parts you did not touch.

Limits#

Organisation limits
Limit	Value
Organisations one user may create	5
Members per organisation	100
Outstanding invitations per organisation	50

Things worth knowing#

Exiting the wizard signs you out. The Exit control confirms with a button labelled "Exit and sign out", and it means it. Your draft survives in the browser, your session does not.
Finishing the wizard does not get you into the product. Creating your first organisation puts your account into review. Read Why a new workspace starts pending.
The wizard does not check whether you already have an organisation. Navigating directly to /onboarding renders it again. Normal navigation never sends an existing member there.
An entity slug that collides with an existing one in the same organisation is rejected with ENTITY_SLUG_TAKEN. Slugs need only be unique within an organisation, not globally.