Data Model
Nevis ID uses nevisIDM as its identity management backend. The data model is pre-configured with three nevisIDM Clients, each serving a distinct purpose.
Clients
In nevisIDM, a Client is a data partitioning boundary — users, profiles, and policies are always scoped to a Client.
| Client | ID | Purpose |
|---|---|---|
| Default | 100 | End users registering and authenticating through your application |
| API | 30 | Technical accounts for programmatic API access |
| Admin | 60 | Administrators and support staff accessing management interfaces |
Default
The Default client is the standard nevisIDM client for end users. It holds the profiles of users who register and authenticate through your application.
The policies of the Default client are patched to offer greater compatibility, for example by allowing all credential types and making firstname and lastname optional.
The Main application is assigned to this client, enabling terms and conditions management for end users.
API
The API client holds technical (service) accounts that call Nevis APIs programmatically. Users in this client receive all Nevis roles by default, allowing them to access the full API surface:
nevisIdm.SelfAdmin,nevisIdm.RootnevisMeta.user,nevisMeta.adminnevisAdapt.user,nevisAdapt.admin
Use this client when you need to create service accounts for system-to-system integrations.
Admin
The Admin client holds human operator accounts — administrators and support staff who use the Nevis management UIs. Like the API client, users in this client receive all Nevis roles by default.
Use this client for all accounts that manage the Nevis ID instance.
Main Application
The Main application (ID: 1000) is a nevisIDM application assigned to the Default client.
The nevisIDM Terms & Conditions Acceptance pattern only prompts a user to accept terms if the user holds a role for the application the terms belong to. The Default client's default profile policy assigns the role Main.terms to every end user, which means all end users are asked to accept the terms defined under the Main application.
You can manage terms and conditions via the management console, as described in Terms and Conditions with Consent Management.