Organization Settings
Feature Detail
Description
Organization Settings provides administrators with a centralized control panel to configure their tenant's operational parameters within the Meander platform. Settings include basic profile data, contact information, data retention policies, and time-bounded support access grants for Norse Global Admins. Admins control organization-wide defaults that govern how their Meander instance behaves for all members without requiring engineering intervention.
Sources & reasoning
The source explicitly lists "Organisasjonsinnstillinger og terminologikonfigurasjon" as a Phase 1 MVP deliverable for the Admin Web Portal. The support-access grant is a named architectural requirement in the Core Roles section, making this screen mandatory before any other org-scoped admin work can proceed.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
Organization Settings is foundational to the multi-tenant architecture. Without a dedicated settings surface, each organization is locked into a generic configuration that fails to reflect their operational realities. The support-access grant mechanism - time-bounded access for Norse Global Admins - is a hard tenant-isolation requirement: without it, Global Admins either have no support path or unchecked permanent access, both unacceptable. This feature enables compliance with data governance expectations across all four partner organizations and reduces support overhead by giving Org Admins self-service control. It anchors onboarding for every new tenant.
Organization Settings is backed by the organization_settings table (one-to-one with organizations). The Admin Web Portal renders it as a server-side-rendered Next.js page under /admin/settings. Support access grants must enforce expiry server-side, not just UI-side, and every grant or revocation must emit an audit_log entry. Fields should use optimistic updates with server validation. The page is gated behind Org Admin and Global Admin roles. Version the settings schema to support non-breaking additions as new modules are introduced. WCAG 2.2 AA compliance required for all form elements.
Components (47)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.