User CRUD
Feature Detail
Description
User CRUD provides organization administrators with full lifecycle management of user accounts within their tenant. Admins can invite new users via email, view and edit profiles, deactivate accounts, and remove users permanently when required. The feature enforces strict multi-tenant isolation, ensuring each organization's user records remain separated from other tenants. It is the foundational capability enabling all peer mentor and coordinator operations across the platform.
Sources & reasoning
Lines 325-328 explicitly place Brukeradministrasjon (invite, deactivate, role assignment) in the Admin Web Portal MVP scope. Without user CRUD the organization cannot onboard any peer mentors or coordinators, making the platform non-functional. It is the prerequisite for all other admin portal capabilities and directly referenced in the Phase 1 MVP deliverables.
-
docs/source/likeperson.md · line 325-328- Brukeradministrasjon (invitere, deaktivere, rolletildeling)
Analysis
User CRUD is the foundational capability of the Admin Web Portal - without it, organizations cannot onboard peer mentors or coordinators, making all other features inoperable. The ability to invite, manage, and deactivate users drives operational continuity across all pilot organizations. From a compliance perspective, accurate user records are required for Bufdir reporting and tenant data isolation. Reducing manual onboarding overhead saves coordinator time and ensures role assignments remain accurate as volunteer rosters change across seasons and organizational cycles.
Implemented as a Next.js SSR admin section backed by the shared REST API. Invitations generate time-limited signed tokens delivered by email; acceptance completes registration. Deactivation is a soft-delete preserving audit history and activity records. Multi-tenant isolation enforced at the API layer via authenticated org context - no cross-tenant data leakage. Pagination and search are required given NHF's 1,400 lokallag scale. All destructive operations require confirmation and are written to the audit trail for compliance.
Components (9)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.