> For the complete documentation index, see [llms.txt](https://docs.varbase.vardot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.varbase.vardot.com/developers/varbase-eca/remote-video-consent.md).

# Enable consent management for remote video

The **Enable consent management for remote video** ECA workflow turns on the matching **Klaro** consent app when a remote video is added, so a YouTube or Vimeo video only loads after the visitor has given consent.

This model is provided by the **Drupal CMS Media** recipe (`drupal_cms_media`). The screenshot below shows the model open in the **Workflow Modeler**.

![The Consent for Remote Video Model Open in the Workflow Modeler](https://410909369-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcuWLZ87gvtX5vA2YGD%2Fuploads%2Fgit-blob-4cf52501b52cdfe027e9d05e9806a543b9a21494%2FWorkflow%20Modeler%20-%20Consent%20for%20Remote%20Video.png?alt=media)

## How It Works

The workflow covers two situations:

* **Event, Insert remote video**: When a remote video media item is created, the workflow decides which provider it is (YouTube by default, or Vimeo when the video URL contains `vimeo.com`), reads that provider's **Klaro** consent app, and enables it. It switches to the administrator account to do so.
* **Event, Save config**: When a YouTube or Vimeo **Klaro** app is saved, if the app was active and is being turned off, the workflow re-enables it, keeping consent management in place for the video providers.

The effect is that embedded YouTube and Vimeo videos are always covered by a consent banner, so no third-party video loads until the visitor agrees.

## Viewing the Model

Go to **Administration** \ **Configuration** \ **Workflow** \ ***ECA***, find **Enable consent management for remote video**, and open it in the **Workflow Modeler**.