How to Apply a Policy to a Video Component Inside a Core Carousel (Panel Container) in Editable Templates?

[RahulSi13]

I have a use case where the Video component is allowed both directly on a page and as a slide inside the Core Components Carousel (v1) using editable templates.

When I add the Video component directly to a page, I can assign a policy that enables embeddable options (e.g., YouTube, Marketo) via the template editor.

When I add the Video component inside the Carousel (as a slide/panel), I do not see the option to assign or inherit the same policy for embeddable options. The Video dialog inside the Carousel does not show the "Embeddable" dropdown, even though the Video component is allowed as a child.

Questions:

1.How can I ensure that the Video component inside the Carousel inherits or references the same policy as the standalone Video component, so that embeddable options appear in the dialog?

2. Is there a way to configure or map the Video policy for the Carousel’s panelcontainer in the template editor, or does this require manual changes in CRX/DE?

3. If manual CRX/DE configuration is required, what is the recommended way to reference the Video policy under the Carousel’s panelcontainer policy node?

Any guidance or best practices for this scenario would be appreciated!

[RahulSi13]

@arunpatidar 

[HrishikeshKagne]

Hi @RahulSi13 ,

1. Inheritance of policies -> A Video inside a Carousel won’t automatically pick up the standalone Video policy. Each container (like Carousel’s panelcontainer) needs its own policy config.

2. Template editor config -> In the editable template, open the Carousel’s Panel Container policy, and under “Allowed Components,” enable the Video component. Then assign or create a Video policy there (just like you did at the page level). No CRX/DE hack needed.

3. If you must in CRX/DE -> You’d copy/reference the same cq:policy path used by the standalone Video into the panelcontainer node’s cq:policy config. But the best practice is to do it in the Template Editor so it’s upgrade-safe and maintainable.

 configure the Video policy inside the Carousel’s panel container policy in the Template Editor; avoid manual CRX edits unless absolutely necessary.

[SantoshSai]

Hi @RahulSi13,

Policies don’t auto-inherit into container contexts. The Video/Embed you drop inside a Carousel uses the Carousel’s panel container policy, not the page’s.

Here is how you can fix (Template Editor - best practice):

1. Open your page’s editable template - select the Carousel - Edit policy.

2. In Allowed Components, enable Video (or Embed if you need YouTube/Marketo) and assign the same policy you use at page level (reuse the existing policy by name). This makes the same dialog options appear inside the Carousel. https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/wcm-components/c...

Sanity check: The “Embeddable” dropdown is a feature of the Core Embed component (YouTube/Marketo processors), not Core Video. If you need those providers, use Embed (or a Video extension that adds embeddables). 
https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/wcm-components/e...

CRX/DE (only if you must): Put changes in /conf policies—not under /apps. Reuse the same policy node the standalone component uses by referencing it for the panel container’s allowed component mapping (property cq:policy). But prefer the Template Editor so it stays upgrade-safe.

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/dev...