Submit models for review and manage updates

Review the complete model#

1. Check model name, slug and every tag.
2. Read the public description and verify linked media and resources.
3. Check collection defaults and each tag override.
4. Confirm provider audiences, fees and availability methods match your intended rights.
5. Submit the collection for review from Console and inspect the returned status.

Track the result#

Keep draft, submitted or pending-review, accepted and rejected/requested-change states distinct. A successful save or an API response does not establish approval. Return to the collection for the current review outcome and any required changes.

Update an existing model#

Edit the intended collection or tag, describe the change clearly and review any new approval requirement. Changes to public availability or commercial terms may be staged pending review; inspect the effective state before informing providers of a new policy.

API boundary#

The current Creator remote-token scope map covers catalog and model writes. It does not establish a supported remote-token submit-review permission. Use the Console review action instead of assuming a catalog write token can approve or publish a model.

Verify the public result#

After approval, check the model’s visible name, tags and access settings on the relevant public/catalog surface. Confirm actual serving capacity separately; publication of metadata does not start a provider device.