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.