Admin Panel

Overview

The Admin Panel is the tenant-scoped administration screen where an organization manages its own users, roles and system health. It brings user creation, role/password changes, activation/deactivation, audit log review and database backup together in one panel. It should not be confused with Platform Management: the Admin Panel only sees your own organization's data, whereas Platform Management is a cross-tenant axis protected by a separate permission flag (is_platform_admin).

Key Concepts

• RBAC roles — five fixed roles: admin, plm_config, quality, supply_chain, viewer_readonly. admin holds every permission (*); the other roles are limited to module-scoped permission sets (e.g. plm_config → PDM/MBOM/DPP/Nuve Recipe/Fashion PLM management and connector synchronisation; quality → issue status and evidence creation, Fashion PLM approval; supply_chain → issue status, connector packaging, Fashion PLM material editing).
• Module entitlement — the modules an organization has purchased (Organization.enabled_modules) form a separate axis; even if a user's role is correct, access is refused with a 403 if the organization has not purchased that module.
• Audit log — a record of every authorisation decision with time, actor, role, action, object and outcome (Allowed/Denied).
• Repository health — schema version, storage mode, audit/snapshot counts, migration list and namespace distribution.

Typical Workflow

1. Open Admin Panel from the left-hand menu; the default tab is Users.
2. Create an account with + New User by entering a username, email, role and password.
3. Use the search/status filter in the user list; change a user's role from the inline drop-down, or assign a new password with Password.
4. If needed, Deactivate a user or bring them back with Activate.
5. On the Roles & Permissions tab, review each role's risk level and permission list.
6. On the Audit Log tab, review past authorisation decisions (especially the denied ones).
7. From the System tab, take a database backup and check repository health (namespace distribution, migration status).
8. On the My Subscription tab, view the modules your organization has purchased, read-only.

Feature Reference

• User CRUD: creation, role change, password change, activation/deactivation
• User list with search and status (active/inactive) filters
• Audit log: actor/role/action/object/outcome record of every authorisation decision
• Roles & Permissions: each role's description, risk level and full permission list
• System: one-click database backup, repository schema/migration/namespace status
• Notification subscription management (per-user notification preferences)
• My Subscription: a read-only list of the modules the organization has purchased

Constraints / Known Limits

• The system's default admin user cannot be deactivated or have its role changed from this panel (it is specially protected in the interface); if it needs resetting, that must be done manually on the server.
• Authorisation works with the demo role model; moving to an SSO/OIDC-based, user-level policy engine is recommended for production.
• Module entitlement and role permissions are two separate layers — even with the right role, access is blocked if the organization has not purchased the module; the two layers must be checked separately.