# Including collections from automation hub in ansible-navigator environment

**URL:** <https://forum.ansible.com/t/including-collections-from-automation-hub-in-ansible-navigator-environment/44605>\
**Category:** Get Help\
**Tags:** azure, vmware, ansible-navigator, aap, galaxy-ng, ee\
**Created:** [October 2, 2025, 10:50pm UTC](https://forum.ansible.com/t/including-collections-from-automation-hub-in-ansible-navigator-environment/44605 "2025-10-02T22:50:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![francis](https://avatars.discourse-cdn.com/v4/letter/f/ac8455/32.png) [@francis](https://forum.ansible.com/u/francis)\
**Post date:** [October 2, 2025, 10:50pm UTC](https://forum.ansible.com/t/including-collections-from-automation-hub-in-ansible-navigator-environment/44605/1 "2025-10-02T22:50:12Z")

</div>

We use Ansible Automation Platform in Azure.  
In AAP, I’m using Execution Environment ee-supported-rhel8, plus additional collections defined in my project:/collections/requirements.yaml file (community.general, community.vmware & checkmk.general)

I would like to follow the same pattern in ansible-navigator.

In ansible-navigator I use the same EE, defined in ansible-navigator.yaml as follows:

execution-environment:  
enabled: true  
image: platform..ansiblecloud.redhat.com/ee-supported-rhel8  
pull:  
policy: missing

But playbooks requiring community.general, community.vmware & checkmk.general fail because the required collections are missing in ansible-navigator environment.

I note, that the AAP / Automation Content / Collections / community.general / Distributions / “CLi configuration” field when copied and pasted produces the following:

[galaxy]  
server\_list = community

[galaxy\_server.community]  
url=https://platform..ansiblecloud.redhat.com/api/galaxy/content/community/  
token=

Can I use the “CLi configuration” data in ansible-navigator some way to include/add/import these collections into ansible-navigator environment. If so where do I configure it?

NB: I’d rather follow the same pattern in ansible navigator rather than building a custom EE (including those collections).