# playbook having include in AWX

**URL:** <https://forum.ansible.com/t/playbook-having-include-in-awx/35850>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [October 12, 2021, 11:41am UTC](https://forum.ansible.com/t/playbook-having-include-in-awx/35850 "2021-10-12T11:41:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ashutosh\_kumar](https://avatars.discourse-cdn.com/v4/letter/a/b19c9b/32.png) [@ashutosh\_kumar](https://forum.ansible.com/u/ashutosh_kumar)\
**Post date:** [October 12, 2021, 11:41am UTC](https://forum.ansible.com/t/playbook-having-include-in-awx/35850/1 "2021-10-12T11:41:10Z")

</div>

I have a playbook which is including another playbook.  
Say Parents.yaml includes child1.yaml and child2.yaml. To run the Parents.yaml from AWX I kept inside the projects directory /var/lib/awx/projects/plays. But while creating the template I see all three playbooks. I do not want to expose child playbooks to template.

Is there any ways I can hide child1.yaml and child2.yaml while creating the template ?

---

<div class="post-metadata">

**Author:** ![Divided\_by\_Zer0](https://avatars.discourse-cdn.com/v4/letter/d/c89c15/32.png) [@Divided\_by\_Zer0](https://forum.ansible.com/u/Divided_by_Zer0)\
**Post date:** [October 13, 2021, 7:25am UTC](https://forum.ansible.com/t/playbook-having-include-in-awx/35850/2 "2021-10-13T07:25:56Z")

</div>

The playbook is visible when creating the template, but the one creating the template is the one responsible for selecting which playbook to run from it. Once you’ve created the template, users cannot change which playbook it runs without changing the template.

---

<div class="post-metadata">

**Author:** ![ashutosh\_kumar](https://avatars.discourse-cdn.com/v4/letter/a/b19c9b/32.png) [@ashutosh\_kumar](https://forum.ansible.com/u/ashutosh_kumar)\
**Post date:** [October 13, 2021, 1:19pm UTC](https://forum.ansible.com/t/playbook-having-include-in-awx/35850/3 "2021-10-13T13:19:28Z")

</div>

Agree. But we cant execute child playbook directly . hence we do not want to expose/display those child playbooks itself to avoid human error.
