Studios and app builders can work with people they already represent or with a separate contributor pool. These models solve different sourcing problems, but both need traceable permission and scope checks.
A customer-owned roster starts with existing relationships
A studio may already manage talent relationships, releases, and client approvals. Connecting that roster to an AI video workflow can reduce duplicate data entry, but the integration must preserve the studio's authority, agreement versions, and access controls.
The product should not infer permission because a person appears in an internal directory. Each asset needs an appropriate record and a use scope that can be matched to the production request.
A contributor pool adds enrollment operations
A contributor pool may offer a broader set of available participants, but it adds identity, consent, media capture, terms, client screening, moderation, reporting, and payment requirements. Every one of those operations needs a reliable owner and reviewed service path.
The pool should explain who can browse, what information is visible, how clients request a license, and how contributors control future participation. It should not imply that a profile listing grants immediate access to generate.
Use one policy model across both sources
Even if assets come from different sources, a consuming application benefits from a consistent way to check scope, status, restrictions, and applicable terms. Source-specific details can remain attached to the record without changing what the production workflow must verify.
Keep identity verification status, signed agreements, client contracts, provider eligibility, and generation usage distinct. That lets the system apply the correct checks without flattening different responsibilities into one ambiguous approval.
Choose based on operating readiness
A team should evaluate who owns each relationship, how rights evidence is collected, who resolves exceptions, and which API can enforce the rules before choosing a source model. A pilot can start with a tightly scoped roster and grow when operations are ready.
Approved.video is intended to support studios and app builders integrating their own talent or a contributor pool. The marketplace remains gated until authorized verification, legal, payout, and generation paths are connected.
CLARIFICATIONS
Questions & answers
Can a company use both its own roster and a contributor pool?
Yes, if the workflow can distinguish asset source, authority, terms, and required review for each record.