MarketScale provides a structured approval process for video content to ensure quality and control over published materials. Below is an overview of how the process works and the roles involved.
Two separate approval surfaces. MarketScale uses two distinct places to manage content approval, and they do not overlap:
Inbox: Used for content created through Upload and Record (content submitted directly to the platform).
Collector: Used for content submitted in response to a Request. Every Request has its own Collector, scoped to that Request.
Request submissions never appear in the Inbox, and Upload or Record submissions never appear in a Collector. Which surface you use is determined entirely by how the content was created.
Overview of the Approval Process
When content is created on MarketScale, it enters one of two approval surfaces based on the creation path:
Upload and Record content routes to the Inbox. Users with approver permissions review and approve it there. Once approved, the content becomes available on the Channel feed.
Request submissions route to that Request’s Collector. The Request creator and any collaborators added to the Request review, approve, and publish submissions from the Collector. Request submissions do not flow to the Inbox at any point.
Notifications are sent to relevant users to confirm the approval status in either surface.
User Roles and Permissions
The ability to approve content in MarketScale depends on the user’s role and the creation path:
Admins: Admins can approve any Upload or Record content in the Channel Inbox. They are global approvers for Inbox content. Admin status alone does not override collaborator settings on an individual Request’s Collector; Request approval is controlled by the Request’s collaborator configuration.
Standard Users: Standard users cannot approve content unless they are granted approver permissions through one of the creation paths below (Upload, Record, or Request). They will see approval requests only for content they are assigned to approve.
How Approvers Are Assigned by Creation Path
Approver assignment works differently depending on how the content is created. This is intentional product behavior.
Upload (routes to Inbox): The person uploading chooses an approver in the Select approver field during the upload flow. If no one is chosen, the uploader is set as the approver by default.
Record (routes to Inbox): There is no approver picker. Every user added to the recording room is automatically granted approver permissions for content created in that room. This is by design: anyone creating content in a shared room can also approve it.
Request (routes to the Request’s Collector): Approver permissions are controlled through the Request’s collaborator settings. The Request creator, plus any users added as collaborators, can approve and publish submissions from that Request’s Collector. Use the Request workflow when you need granular approver control. Request content never enters the Inbox.
Steps to Approve Content in the Inbox (Upload and Record)
From the dashboard, navigate to your Channel Inbox.
Review the Upload or Record content awaiting approval.
For each item, select the option to either approve or reject the content.
Once approved, the content will be published to the Channel feed and accessible to other users.
Steps to Approve Content in a Request’s Collector
Open the Request you want to review.
Navigate to the Request’s Collector to see submissions against that Request.
Review and approve or reject each submission. Only the Request creator and configured collaborators can take action here.
Approved submissions can be published directly from the Collector.
By following these steps and understanding the roles and surfaces involved, users can efficiently manage the approval process for video content in MarketScale.