Provider approval and legal permission answer different questions. One concerns a provider's own access or content process; the other concerns authority to use people, works, or other assets under the applicable terms.
A provider response has a specific source
A model or platform provider may review whether an asset or request meets its own program requirements. The decision belongs to that provider and may depend on the account, model, region, use case, and submitted materials. A team should preserve those details with the response.
The decision should not be paraphrased as a blanket statement that a campaign is legally cleared. It may only address provider eligibility or a specific platform policy. If the campaign changes, the old response may not cover the new request.
Permission comes from the relevant rights and terms
A rights holder or authorized representative may grant permission under an agreement. The scope of that permission can be limited by media, duration, territory, category, client, or other conditions. Those limits should be reviewed against the proposed use.
A provider cannot grant rights that it does not hold simply by accepting an asset into a system. Similarly, a release from a person may not resolve every issue involving music, trademarks, source footage, or third-party contracts. Ask counsel to evaluate the complete context.
Represent both checks in software
Use distinct statuses for rights evidence, internal review, provider submission, and provider response. Store the decision source, date, asset, organization, and conditions. If a check has not happened, use a clear unavailable or pending state instead of a guessed outcome.
When required conditions do not align, block the next step and explain the specific gap. That is more useful than returning an undifferentiated error or offering a retry that cannot resolve the underlying permission issue.
Build around the real boundary
A studio workflow can coordinate records and handoffs while leaving final decisions with the authorized people and providers. This boundary helps product teams avoid a false promise that a status badge or API response can replace all review.
Approved.video is designed to connect rights and review records to studio and application workflows. Its provider submission and generation actions remain dependent on authorized integrations, so a locally recorded status must never be presented as a provider decision.
CLARIFICATIONS
Questions & answers
Does provider approval prove that the rights holder consented?
No. Provider review and rights-holder permission are different checks and should be represented separately.