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. Most of what the dashboard files under Organization is stored per workspace instead, and that distinction 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.
Branding is dashboard-only
The branding endpoints are operator-internal and are not in the public API. There is no supported way to manage branding from your own system. If you need one, email engineering@kontier.eu.
Team and access
Members, invitations and roles live here. Roles bundle permissions, and the dashboard lists exactly what each one grants, which is a better reference than any table we could keep in sync here.
The catalogued settings
Under Organization the dashboard also exposes a keyed settings store: invoicing behaviour, e-invoicing preferences, notification targets. Two things to know before you rely on it.
It is stored per workspace. Despite the name and the API path, these values live against the workspace you are in. Setting one in sandbox does not set it in live.
It accepts keys it does not know. The store does not reject an unrecognised key, so a typo is saved rather than refused, and then read by nothing. If a setting appears to have no effect, check the spelling before checking the behaviour.
Some settings you may be looking for are not tenant settings
Grace periods, suspension delays and hold durations are deployment configuration, set by whoever runs the installation. They are not exposed to you, and no amount of looking in the dashboard will find them.
Usage retention is deployment-level for a structural reason: usage events are partitioned by time alone, so retention cannot be applied per tenant.
Reference
| Topic | When you need it |
|---|---|
| Settings | Which scope holds which value |
| Workspaces | What differs between live and sandbox |
| Entity settings | Defaults that records copy or read |
| Taxes | Tax rules, as distinct from your tax identity |
| Organization API | Profile and tax profile endpoints |