Identity Foundation¶
Status: Implemented
Overview¶
The Identity Foundation establishes the minimum identity model required by the Nivron platform. It introduces organizations and users as first-class platform entities, providing the basis for future authentication, authorization and multi-tenant capabilities.
Objectives¶
- Support multiple organizations.
- Isolate tenant data.
- Provide stable UUID v7 identifiers.
- Prepare the platform for RBAC and IAM.
- Keep identity independent from business modules.
Current Domain Model¶
| Entity | Purpose |
|---|---|
core.organizations |
Represents a tenant within the platform. |
identity.users |
Represents a platform user belonging to an organization. |
Relationship¶
erDiagram
ORGANIZATIONS ||--o{ USERS : contains
ORGANIZATIONS {
uuid uuid
string slug
string name
string status
}
USERS {
uuid uuid
string username
bigint organization_id
string status
}
Design Principles¶
Organization First¶
Every user belongs to exactly one organization. Business modules should always operate within an organizational context.
Stable External Identifiers¶
Public references use UUID v7 instead of sequential database identifiers.
Future Expansion¶
The current model is intentionally minimal and is expected to evolve with roles, permissions, groups, service accounts and authentication providers without breaking existing entities.
Planned Evolution¶
| Capability | Status |
|---|---|
| Organizations | Implemented |
| Users | Implemented |
| Roles | Planned |
| Permissions | Planned |
| Groups | Planned |
| Service Accounts | Planned |
| API Tokens | Planned |
| SSO Providers | Planned |
Related Topics¶
- Database Architecture
- Platform Framework
- Control Plane
Next Step¶
Continue with API Architecture to understand how platform capabilities are exposed through versioned interfaces.