Skip to main content

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. Inside an organisation a person can also be limited to particular sites, so a site contact sees only their own building's kit; see Sites.

Branding​

Each organisation can look like its own service. Under Settings, Organisation, Branding an administrator can set:

  • an accent colour, used across the app so clients are told apart at a glance;
  • a service name, shown at the top of the app, in the browser tab, on the sign-in page and on the staff issue form instead of "Tagaris" (call it "Assets" or "IT register" if that is what your people know it as);
  • a logo (PNG, JPEG or WebP, up to 1 MB), shown in the same places instead of the Tagaris mark. It is served from the organisation's own address on this server and stored with your photos, so backups include it.

The sign-in page is shared by every organisation on the server, so it shows the branding of the organisation single sign-on is set up for, or the first one created. Emails, the mobile app and the documentation still say Tagaris.

Cross-org groups: one role across many organisations​

Inviting every engineer into every client organisation does not scale, so the install owner can define cross-org groups (Settings, then Application, then Cross-org groups). A group grants one role, and optionally a set of permissions, 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, and the group's permissions apply in every organisation it covers. A new client organisation added to the "All engineers" group is immediately accessible to the whole team.

Creating a cross-org group or adding members needs the multiple organisations add-on, because a group grants access without a membership. A group above view only, or with a permission, uses a seat in each organisation it covers.

Roles, access groups and seats are described in Roles and access.

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. Seats are counted per organisation, and the install owner never uses one anywhere. See Licensing for how keys work.