This topic describes how the metadata assurance (required fields) feature interacts with media sharing. The Video Cloud media sharing feature enables sharing videos from one account (the sharer) to another (the sharee). This creates a copy of the shared video in the sharee account, including the video's metadata. The metadata assurance feature lets you designate which metadata fields are important for your business purposes and then require your users to complete the required metadata fields for new videos before the videos can become active. You can configure how required fields behave in the media sharing context.
When you receive shared videos into your account using media sharing, you can't always be sure that all the accounts the videos came from have the same required fields as your account. How required metadata fields behave depends on how you have configured how to accept shared videos. Each Video Cloud publisher can determine for their account whether videos shared to them must be manually approved before they become active, or whether they will be automatically approved as soon as they are shared.
By default, Video Cloud enforces metadata assurance for videos that are shared to your account. When metadata assurance is enabled for shared videos, the behavior is as described under Manual acceptance or Automatic acceptance. When metadata assurance is disabled for shared videos, then automatically accepted shared videos can become active even if they are missing one or more required metadata fields.
You can disable enforcement of metadata assurance in the Video Cloud Studio:

If you use manual approval for shared videos (the default):
If you use automatic acceptance for shared videos:
If a video that has already been shared and accepted is shared again, its metadata can be updated, but its active/inactive state is not changed. It is possible that when a video is re-shared, some required metadata field could be blanked out. A re-shared video won't be checked for the presence of required metadata fields unless it is inactive and you try to activate it, or you edit its metadata.