Multi-brand
Purpose
One organisation, several public faces: brands make it possible to trade under different names without running several installations or maintaining master data twice.
The decision behind it is deliberate: what belongs apart is kept apart — documents, appearance, ownership. What is shared stays shared — customers, products, contacts.
Scope
- Its own appearance per brand: legal company name, logos and a colour scheme for outgoing
communication.
- Documents and work items belong to a brand. Number schemes, templates and sending accounts can
be held per brand — with a cross-brand edition as the safety net, so that only the difference is maintained rather than every brand separately.
- Master data stays brand-neutral. A customer is a customer, regardless of which brand sold them
something.
- Permissions take effect per brand. What counts is the permission in that brand, not mere
membership, see Roles & permissions.
- The brand picker in lists appears only when there is something to choose.
Interplay
The brand shapes above all communication — sending account, mail layout, footer — and the documents from the commerce core. Settings can be held system-wide or per brand.
Limits
- Not a tenancy model. Brands separate documents and appearance, not the database. Anyone needing
genuine separation of separate companies runs separate installations.
- A brand's short name is permanent. It surfaces in places that cannot all be carried along.
- Product documentation is brand-neutral. This documentation describes the product, not a
particular brand.
- Moving a document to another brand requires the permission in the target brand, not only in the
original one.