The quiet cost of many logins
In a multi-site operation, the same person shows up in a surprising number of systems. A new instructor is created in the rostering tool, again in payroll, again in the access system, and perhaps once more wherever finance or governance can see them. Each of those is a separate account, created by hand, kept current by hand, and removed by hand when the person leaves. None of it is hard, and that is exactly why it is easy to get wrong.
The cost of many logins is quiet but real. It is the administration of setting a person up several times. It is the inconsistency when one system says a person has access and another has not caught up. And it is the security gap when someone leaves and an account in one of those systems is forgotten. A shared identity layer is the structural fix, and it is one of the underrated benefits of running on a platform rather than a stack.
What one identity actually means
One identity means a person is a single account across every product, not a set of separate accounts linked together. This is more than single sign-on. Single sign-on puts one login in front of several separate accounts, which still have to be created and removed in each system. One identity means there is a single account to begin with, shared across the products on one control plane, with access granted as roles rather than re-created per tool.
The difference shows up at the moments that matter: joining, changing role, and leaving. With one identity, a person is set up once and given the access their role needs. When their role changes, the change takes effect everywhere. When they leave, removing their access removes it across the platform at once, rather than depending on someone remembering every system they touched.
Why it matters most across many sites
A single-site business can keep on top of a handful of accounts by attention alone. A multi-site operator cannot. Staff move between venues, casuals come and go, and access needs change with the season. The volume of identity changes is high, and the cost of getting them wrong, an account that lingers or access that does not match the role, rises with the number of sites and systems.
One identity turns that from a manual, error-prone chore into a single, consistent action. It is simpler to administer, because the work happens once. It is easier to keep secure, because access is managed in one place and deprovisioning is immediate and complete. For an operator running several venues or brands, that is a meaningful reduction in both effort and risk.
How the Cohiva suite shares identity
Cohiva is built as one platform with purpose-built products on top, sharing one identity and one control plane. A person onboarded in Culture, rostered against a venue in Complex and named on a resolution in Quorum is one identity, not three accounts to keep in step. The same holds across Crunch, Control, Sign, Campaign and Campus.
Because identity is shared structurally rather than linked after the fact, the join is always live. Granting and removing access is a single action that the whole platform respects, which is the practical payoff of one control plane.
One identity, one data layer, one bill
A shared identity is one of three things an integrated platform brings together, alongside one data layer and one commercial relationship. They reinforce each other. Shared identity means a person is recorded once. A shared data layer means the records that person touches are also recorded once. And one bill means the platform is bought and grown as a whole, rather than as a tangle of separate contracts.
For an operator, the combined effect is that the operation runs on one set of people, one set of records and one relationship, instead of a patchwork that has to be reconciled and re-administered at every join.
Where to go next
To see the data side of the same model, read one platform, one data layer and how data flows across the Cohiva suite. For the cost argument behind running on a platform, read the total cost of a multi-site software stack.
To see the products that share the identity layer, start from the products hub.