1.2.3 Admin vs User Areas — Scope, Access, and Responsibilities

Praisma Hub clearly separates administrative areas from user-facing areas. This separation is essential for security, usability, and compliance, especially in public-sector and enterprise environments.

Separation of Concerns

The platform distinguishes between:

Administrative areas, used for configuration, governance, and oversight

User areas, used for daily operational work such as content creation and communication

This separation ensures that sensitive configuration and system-level controls are not exposed to regular users.

Administrative Areas

Administrative areas are accessible only to users with elevated permissions.

Typical responsibilities include:

Tenant and organization configuration

User, role, and permission management

Domain and integration settings

Workflow and approval configuration

Quota, usage, and subscription management

Audit logs and system monitoring

Administrative users operate with a high level of responsibility and accountability.

User Areas

User areas are designed for day-to-day operational tasks, such as:

Creating and editing CMS content

Managing media assets

Responding to inbox messages or surveys

Viewing analytics relevant to their role

Participating in workflows and approvals

User interfaces are intentionally focused and simplified to reduce error risk and improve productivity.

Access Enforcement

Access to admin or user areas is enforced through:

Role-based access control (RBAC)

Permission checks at route, service, and UI level

Tenant and organization context validation

Users only see what they are authorized to access, both functionally and visually.

Security and Compliance Implications

The strict separation between admin and user areas supports:

Reduced attack surface

Clear accountability and audit trails

Compliance with BIO, ENSIA, and internal security policies

Safer delegation of responsibilities

Summary

By separating administrative and user areas, Praisma Hub ensures that governance, security, and daily operations can coexist without conflict. This model supports scalable collaboration while maintaining control and compliance.