Units and the organizational hierarchy
How Nevis ID models organizations: units, unit trees with no configured depth limit, profiles that link users to units, and what follows the organizational hierarchy.
Users, profiles, and credentials
How Nevis ID separates the user, the credentials, and the authorizations: one person with one set of credentials, several profiles with separate authorizations, the active profile of a session, and actions that stay attributable to one person.
Applications, roles, and enterprise roles
How Nevis ID models what people are allowed to do in your applications: applications that own roles, authorizations that assign a role to a profile, and enterprise roles that bundle roles across applications.
Tenants and isolation
How Nevis ID keeps user populations apart: a dedicated instance per customer, the environments of an instance (TEST and LIVE by default), and tenants inside an instance with their own users, units, and policies.
Delegated administration
How delegated administration works in Nevis ID: administrator roles, the scope that limits a role to tenants, units, applications, and enterprise roles, and the rules that keep delegation within bounds.
B2B organization structures
How Nevis ID models partner companies: a partner company as a unit in the unit tree, user administration by the partner company while you keep control of the authorizations, application roles and enterprise roles as the access of its people, and the B2B, B2B2E, and B2B2C models on units and tenants.