Multi-tenancy

One deployment can serve several independent organisations (tenants), each with its own reports, categories, locations and admin users. The superadmin role manages them at /admin/organisations.

Each organisation has its own reporting link, /submit/<slug> — the one to give its employees:

  • The wizard there offers only that organisation's categories and locations, and files the report under it.
  • The link, with a copy button, is on /admin/organisations (superadmin) and on an organisation admin's dashboard.
  • /submit is the default organisation's (DEFAULT_ORG_SLUG). If that names no active organisation, /submit answers 503 and logs the setting, and a set-up instance refuses to start.
  • An unknown or deactivated slug is a 404. There is no list of organisations, but a slug is part of a public link: anyone can test whether a guessed one exists.
  • A draft stays with the organisation it was started for. Another organisation's link shows a fresh wizard; its first step replaces the draft, and the earlier one is lost to that browser.
  • With multi-tenancy off there is one wizard, at /submit: /submit/<default slug> redirects there, any other slug is a 404.
  • Every account belongs to an organisation. On /admin/users a superadmin chooses it for a new account; an admin creates accounts in their own. Accounts LDAP provisions, and those made before multi-tenancy was switched on, belong to the default organisation.
Variable Description
MULTI_TENANCY_ENABLED Optional Set to true to activate multi-organisation support. Requires at least one organisation to exist; the default org is auto-created at setup. Default: false
DEFAULT_ORG_SLUG Optional Slug of the default organisation auto-created during setup. Used for single-tenant deployments and as the fallback for legacy data. Default: default

Edit this page on GitHub