Organization settings

Your organization is the company. Its settings describe you to the outside world: who you are on an invoice, what tax identity you trade under, how the platform looks to your customers, and who on your team can do what.

These are the settings that genuinely cannot differ between environments. The keyed organization settings work differently: they are set at the organization and inherited by every workspace, which can override them. That ladder is covered in Settings.

✕

The company profile

Name, address, contact details and default currency and locale. This is what appears on documents your customers receive, so it is worth getting right before the first invoice rather than after.

Tax identity

Your own VAT identification and tax profile, which is separate from the tax rules you apply to customers. Rules decide what a customer is charged; the profile is who you are for tax purposes, and it is what makes reverse charge legible on an invoice.

Security

Two-factor requirements and session policy, organization-wide. Because they are organization-wide, tightening them in one workspace tightens them everywhere, which is the behaviour you want and worth knowing before you test it.

Branding

Logos, colours and sender identity, applied to invoices, the customer portal and outbound mail.

Team and access

Members, invitations and roles are managed over the API; see Team and roles. Roles bundle permissions, and GET /v1/roles returns exactly what each one grants in its permissions list.

The catalogued settings

The organization also has a keyed settings store: invoicing behaviour, e-invoicing preferences, notification targets, approval checkpoints, sign-in policy, audit retention, webhook retry limits. Read and write it with GET /v1/organization/settings/catalog (every key and its type), GET /v1/organization/settings and PUT /v1/organization/settings; see Settings. Two things to know before you rely on it.

Values inherit from the organization. Saved from a live workspace, a value lands at the organization and applies to every workspace that has not overridden it. Saved from a sandbox, it lands on that sandbox only and never changes live. A level above can lock a setting or bound the values below it. See Settings for the full ladder.

Unknown keys are refused. Every key is validated against the settings catalog: an unrecognised key is refused (400 VALIDATION, field code UNKNOWN_SETTING), and a value of the wrong type or outside its range is refused too. A typo fails at save time rather than being stored and read by nothing.

Reference