What does multi-tenant mean?

Multi-tenant describes how software separates its customers. One system, many organizations, each seeing only its own data and users.

In practice at an event

The word matters to two kinds of buyer. Agencies running events for several clients want each client’s data separated while their own team works across all of them, without maintaining a different login per client. Groups and federations — a parent body with regional chapters or subsidiaries — want the same shape internally, with a central team able to see across and a local team able to see only their own.

For a single organization running its own events it is invisible, which is as it should be.

What to look for

Ask how the hierarchy works: is it organization, then events, then roles, and can somebody hold a role at one level without inheriting access at another?

Ask specifically whether a per-event moderator can see the attendee list for other events. That is the question a security reviewer will ask, and the answer should be no.

How event67 handles it

event67 is multi-tenant from the first day of its design rather than as a later addition. Roles cover super-admins, org admins and per-event moderators, so a moderator brought in for one event has access scoped to that event. Every administrative action is audit-logged across the hierarchy.

For an agency this is a plausible fit rather than a proven one, and we describe it that way: the multi-tenant structure and branded apps support the shape, and we do not claim a track record we cannot evidence.