continON/Identity & Access
Who someone is, and what they answer for.
continON represents people through the positions they hold in the organization — each position carrying its own responsibilities, and from those, what a person may see and do. This page is about that model, not about corporate security policy.
The model
Access is the consequence, not the starting point — a person’s position and its responsibilities decide what they may see and do.
User
A person, working in the platform through the position they hold.
Role
The responsibilities attached to a position, and from them what a user may do.
Organizational unit
The department, office or entity a position sits in, modeled from the real structure.
Permission
The specific action or view a role is authorized for — nothing beyond it.
Authorized view
What a user sees, from their position: their work, their unit, their level, no more.
Accountability
Every action carries the identity and authorization behind it, in the record.
Why it matters
Structure changes, and access follows.
Because the organization is modeled once and every application reads from it, a change in structure — a new unit, a moved responsibility, a promotion — carries through to what people can access. Access is not maintained separately in each system, where it drifts out of step.
See the model against your own structure.
Your positions and responsibilities, with the access each implies.