Settings
Configuration in Kontier lives at four levels, and the level a value lives at decides who it affects and when.
| Scope | Holds | Example |
|---|---|---|
| Organization | Things true of the company | Company name, tax profile, branding, roles |
| Workspace | Things that may differ between live and sandbox | Invoicing behaviour, e-invoicing, integrations |
| Entity | Things true of one record | A customer's payment terms, a plan's dunning policy |
| Deployment | Things the operator of the installation sets | Grace periods, retention windows |
Deployment settings are not yours to change; they belong to whoever runs the installation. Everything else is.
Settings saved in sandbox do not apply to live
Most of what the dashboard calls "organization settings" are stored per workspace, and sandbox is a workspace. A value you set while in sandbox mode applies to sandbox only. Set it again in live, or it will not be there when it matters.
There is no inheritance
This is the part that surprises people who expect a cascade.
Organization settings and workspace settings are different settings in different places. A workspace does not inherit from its organization and cannot override it, because they do not hold the same keys.
The only fallback that exists is within a single workspace: a setting you have never touched uses its built-in default, and saving a value overrides that default. One level, not a chain.
Code
Entity settings are different: many of them shadow a workspace default, and that cascade is real. It is covered in Entity settings.
What is organization-wide
Seven things cannot differ between workspaces, because they describe the company rather than an environment:
- the company profile and tax identity
- security settings
- branding
- roles, members and invitations
- checkout links
- invoice numbering
- background job limits
Sandbox invoices consume live invoice numbers
Invoice numbering is the sharp edge of that list. The sequence is organization-wide while the prefix is per workspace. Finalising an invoice in sandbox therefore advances the same counter live invoices use, and the gap in your live numbering is permanent.
Preview and draft freely; think before you finalise in sandbox.
Choosing a scope
When you are deciding where to configure something:
| Question | Answer |
|---|---|
| Should it differ between live and sandbox? | Workspace |
| Does it describe the company to the outside world? | Organization |
| Is it true of one customer, plan or subscription only? | Entity |
| Should every tenant on this installation share it? | Deployment, so not yours |
Where to go next
| Page | Covers |
|---|---|
| Organization settings | The company profile, tax identity, security and branding |
| Workspaces | What a workspace isolates, and sandbox |
| Entity settings | Configuration that lives on records, and what it shadows |