Project Member Roles & Permissions
The role each member starts with, and every permission you can fine-tune.
Annie
Last Update 22 天前
ProView follows a zero-trust security model: every member is given access that matches their real role and responsibilities. Each project member holds one of three roles, which sets their default permissions — and a Project Admin can adjust any individual permission at any time.
The Three Roles
| Role | Who they are | Default capabilities |
| Project Admin | The owner of the project | All project permissions by default — manage the project, assets, and tasks; share, publish, download, and delete. |
| Task Admin | Manages the project's day-to-day tasks | Upload and view all assets; manage tasks; share assets for review and approval. |
| Project Member | Every other contributor | Upload assets, view all assets, and share assets for review and approval. |
Note: These are Postudio's defaults. A Project Admin can change any permission for any member at any time using the permissions below.
Member Badges
You can optionally give a member a badge that matches their real-world title — Director, Producer, Showrunner, and more — chosen from the dropdown. Badges are cosmetic only and don't affect a member's roles or permissions.
You can optionally give a member a badge that matches their real-world title — Director, Producer, Showrunner, and more — chosen from the dropdown. Badges are cosmetic only and don't affect a member's roles or permissions.
Fine-Tuning Permissions
To adjust what a member can do, go to their card → Member Actions (...) → Change Permissions. The permissions are grouped into the categories below.
To adjust what a member can do, go to their card → Member Actions (...) → Change Permissions. The permissions are grouped into the categories below.
Project Management
| Permission | What it enables |
| Project Access | Joining and collaborating as a member of this project |
| Project Administration | Modifying project configuration, settings, and operational details |
| Member Management | Managing project members — invitations, removals, and access controls |
| C2E Session Management | Creating and overseeing Camera to Edit sessions in the project |
Assets Management
| Permission | What it enables |
| Upload Assets | Uploading files and folders to this project |
| View All Assets | Viewing every asset in the project, including those uploaded by others |
| Share Folders | Sharing project folders with others, including setting access permissions |
| Asset Metadata Management | Creating, modifying, and maintaining metadata on project assets |
| Delete All Assets | Deleting any asset in the project, regardless of who uploaded it |
Organise Assets
| Permission | What it enables |
| Copy Within Project | Copying assets between folders in the same project |
| Move Within Project | Permanently relocating assets between folders in the same project |
| Copy Between Projects | Copying assets to another project within the same team |
| Move Between Projects | Permanently transferring assets to another project within the same team |
| Copy Between Teams | Copying assets to a project in a different team (also requires Upload Assets on the destination) |
Task Management
| Permission | What it enables |
| Task Lifecycle Management | Creating, assigning, updating, completing, and deleting tasks |
| Launch Cloud System (Project-Level) | Requesting cloud system resources without a task association |
| Launch Cloud System (Task-Level) | Requesting cloud system resources tied to a specific task |
| Live Collaboration | Inviting project members into a real-time cloud session |
Publish Assets
| Permission | What it enables |
| Publish ProHub-Generated Assets to S3 | Transferring cloud system-generated assets to an Amazon S3 destination |
| Publish All Assets to S3 | Publishing any project asset — uploaded or third-party — to Amazon S3 |
| Publish ProHub-Generated Assets to Contido | Distributing cloud system-generated assets to Contido |
| Publish All Assets to Contido | Publishing all asset types to Contido storage |
| Publish Assets to Sprinklr | Sharing project assets with Sprinklr for downstream workflows |
Proxy Asset Sharing and Download
| Permission | What it enables |
| Share Proxy ProView Assets | Sharing watermarked proxy versions of cloud system-generated assets for download |
| Share Proxy Versions of All Assets | Sharing proxy versions of any project asset with external recipients |
| Download Proxy ProView Assets | Downloading proxy versions of cloud system-generated assets |
| Download All Proxy Assets | Downloading proxy versions of all assets in the project |
Original Asset Sharing and Download
| Permission | What it enables |
| Share Original ProView Assets | Sharing original, full-resolution cloud system-generated assets outside the project |
| Share Original Versions of All Assets | Sharing full-quality versions of any project asset with external recipients |
| Download Original ProView Assets | Downloading original versions of cloud system-generated assets |
| Download All Original Assets | Downloading original, full-resolution assets from the project |
Review / Approve Assets
| Permission | What it enables |
| Approver/Reviewer Assignment | Sharing assets with designated approvers or reviewers, including those external to the project |
| Asset Status Management | Modifying the status of any asset in the project lifecycle |
| Asset Approval Authority | Approving assets by setting their status to Approved |
| Public Comment Access | Viewing and contributing public comments on project assets |
| Private Comment Access | Viewing and contributing private, internal comments restricted to authorised members |
Note:
- Copy Assets — enable both Copy Assets and Upload Assets to perform this action.
- Move Assets — enable both Move Assets and Download to perform this action.
Applying These Permissions to Groups
The same permission catalogue applies to groups as well as individual members — a group can be granted a subset of the permissions above, which then apply to all of its members. Groups are configured separately. See Group Permissions for how to set them at the team and project levels.
The same permission catalogue applies to groups as well as individual members — a group can be granted a subset of the permissions above, which then apply to all of its members. Groups are configured separately. See Group Permissions for how to set them at the team and project levels.
Related Articles