Multiple organisations

A Tagaris install can hold more than one organisation, each with its own asset register, people, locations, settings and branding. This is built for managed service providers keeping client registers apart, and for group companies that want one install with clean separation between entities.

The free plan includes one organisation. Creating more needs the Multi-organisation add-on, sold in three sizes (up to 5, 15 or 50 organisations) alongside any Team plan; see the pricing page. For more than 50 organisations, contact us.

How separation works

Every record belongs to exactly one organisation. Assets, people, stock, reports, imports, exports and the audit log are all scoped to the organisation you are working in, and the organisation switcher in the top bar moves between them. Nothing is shared between organisations except the install itself and its user accounts.

Each organisation has its own Settings area: its own email transport, alert thresholds, custom fields, status labels and data export. A client organisation can therefore have alerts sent from its own address and its own branding, independent of the others.

Creating organisations

The install owner creates organisations under Settings, then Application, then Organisations. Members are then invited per organisation with a role, so an engineer can be an Editor in one client's register and have no access at all to another's.

Groups: one role across many organisations

Inviting every engineer into every client organisation does not scale, so the install owner can define groups (Settings, then Application, then Groups). A group grants one role across a chosen set of organisations to a set of people. A person's effective role in an organisation is the highest of their direct membership and any group that covers it. A new client organisation added to the "All engineers" group is immediately accessible to the whole team.

Roles themselves are described in Roles.

Licensing across organisations

Licences are applied per organisation, and the same key can be applied to each organisation on the install; activation counts per install, not per organisation. The add-on's organisation limit applies install-wide. See Licensing for how keys work.