Role-based authorization and approval workflow
MediaPress V6 comes with a "deny by default" authorization layer so everyone sees only the part of the system that's theirs: no one can access anything unless explicitly permitted. You define the roles and assign, down to the field level, which menus and fields each can see and edit. And an approval workflow routes content through an approval chain — nothing goes live until an authorized person approves it.
How you manage roles and permissions in the panel
Role-based access & authorization
Role-based access (RBAC)
Define roles and assign what each can see and edit. Field-level control: who sees and edits which field.
Menu and submenu permissions
Grant each role view and edit permissions on menus and submenus separately. A user sees only the sections they're authorized for; menus they lack permission for don't appear in the panel at all.
Approval workflow & approval chain
Within an approval chain, grant selected users approval-gated publishing rights. Content doesn't go live until an authorized person approves it; you decide who can approve what.
Two-factor authentication (2FA)
Protect admin access with an extra layer. 2FA can be enforced per role for sensitive roles; users with that role must set up 2FA before they can sign in.
Protection against privilege escalation
Users can't assign permissions they don't have. The system prevents granting a role above one's own level or widening one's own permissions.
Login audit log
Who logged in, when and from which IP stays visible. Audit retention is configurable, with advanced visibility and log anonymization controls for super admins.