PV4 uses a role-based permission system to keep instance access secure and clearly scoped. Each user is assigned one or more roles, and each role carries a defined set of permissions.
Default roles
PV4 doesn't currently ship a standard set of roles for customers — there's no built-in role like "Administrator" or "Viewer" assigned out of the box. Every user is assigned a base _Default role automatically; beyond that, you build the roles your show or organization needs — see Custom roles below.
Custom roles
You can also create custom roles with your own combination of permissions — see Guide: Creating a New Role and Guide: Editing an Existing Role.
Permissions
Each role's permissions are set per category, generally at one of three levels: Read (view only), Edit (modify existing items), or Full (create, edit, and delete). Categories include API Keys, Applications, Content (down to access on individual Content Folders), Cues, Transcode Jobs, and others — see Permissions Reference for the complete list of categories and exactly what each permission grants.
Assign roles carefully to maintain security and prevent unauthorized changes.