Multi-company

How multiple companies work in one Sumeru database — and what this is not.

What multi-company is

• One PostgreSQL database
• Multiple core.company records
• Users switch active company via the company switcher in the shell
• Business documents (orders, invoices, leads) carry a company_id
• Record rules can restrict rows by company

Suitable for: one organisation with legal entities, or a holding company running separate books in one instance.

What it is not

• Not multi-tenant SaaS — all customers in one DB would share schema and admins
• Not hard network isolation between tenants
• Not a substitute for separate databases per customer

For SaaS or strict tenant isolation, plan separate databases (or future architecture). See Isolation model.

Daily use

1. Administrator creates companies under Settings → Companies.
2. Assign users to allowed companies.
3. Each user picks active company from the switcher before working.
4. New records default to the active company.

For administrators

• Configure record rules so users only see their companies' data
• System administrators (base.group_system) bypass most restrictions
• Test with a non-admin user before go-live

Related settings

Settings → Users — company access on user form.

What needs an engineer

• Custom record rules per model
• Consolidated reporting across companies
• Inter-company transactions (not standard pre-alpha)

See also

• Settings
• Record rules (developers)

Sumeru is pre-alpha (no tagged release, no upgrades). Part of Project Meru.