# Unable to Assign Team Permissions for Execution Environments — Option Not Listed **URL:** \ **Category:** Get Help\ **Tags:** ansible-tower, security, awx, ee\ **Created:** [July 1, 2025, 3:02pm UTC](https://forum.ansible.com/t/unable-to-assign-team-permissions-for-execution-environments-option-not-listed/43668 "2025-07-01T15:02:31Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![SaravanaSelvaraj](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/saravanaselvaraj/32/2841_2.png) [@SaravanaSelvaraj](https://forum.ansible.com/u/SaravanaSelvaraj)\ **Post date:** [July 1, 2025, 3:02pm UTC](https://forum.ansible.com/t/unable-to-assign-team-permissions-for-execution-environments-option-not-listed/43668/1 "2025-07-01T15:02:31Z")
**Unable to Assign Team Permissions for Execution Environments — Option Not Listed**. Dear community, We are currently using LDAP for managing user access and permissions in AWX. However, we’ve encountered what appear to be two limitations (or possibly bugs): 1. **Copy Button Not Visible for Non-Admin Users** Users with the role **“Normal User”** are unable to see the **copy** icon for job templates, as shown below: ![image](https://us1.discourse-cdn.com/ansible/original/2X/7/72b09e4a8f1c8cf9061c16ce606fbf12ade44093.png) 1. **Non-Admin Users Cannot Access Execution Environments** As an admin, I am able to view and select **Execution Environments** while running job templates. However, users with non-admin roles (like **“Normal User”** ) do not see the all the custom Execution Environments during Job Template execution as shown below. ![image](https://us1.discourse-cdn.com/ansible/original/2X/6/6a9ce0e908daa808c2822965b7c5c545dcfd8aa4.png) And infact they should all the custom EE created. To address this, I attempted to grant access to Execution Environments by assigning permissions to an LDAP group (via Teams in AWX). Unfortunately, the **“Add team permissions”** dialog does **not list Execution Environments** as a resource type: ![image](https://us1.discourse-cdn.com/ansible/original/2X/5/5a66097a82fb5d49e5bc6035bc5359878b95aad2.png) I found [this related GitHub issue](https://github.com/ansible/awx/issues/11689), which confirms that RBAC support for Execution Environments is currently lacking. I’ve tried looking for workarounds but haven’t been successful. Note: If I create a user locally (Not through LDAP) and associate this user to the team , I can see the Execution Environments without any issues as shown below . (devops\_awx\_vault\_lookup) ![image](https://us1.discourse-cdn.com/ansible/original/2X/0/0b74fed8c04bc0ef85c5534e40694bf2e3fe339b.png) If anyone has found a solution or workaround for this, I’d greatly appreciate your input. Thank you! Thanks and Regards Saravana Selvaraj ---
**Author:** ![SaravanaSelvaraj](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/saravanaselvaraj/32/2841_2.png) [@SaravanaSelvaraj](https://forum.ansible.com/u/SaravanaSelvaraj)\ **Post date:** [July 3, 2025, 7:25am UTC](https://forum.ansible.com/t/unable-to-assign-team-permissions-for-execution-environments-option-not-listed/43668/2 "2025-07-03T07:25:47Z")
Can someone please help me on this one ? ---
**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\ **Post date:** [July 7, 2025, 8:11am UTC](https://forum.ansible.com/t/unable-to-assign-team-permissions-for-execution-environments-option-not-listed/43668/3 "2025-07-07T08:11:15Z")
@SaravanaSelvaraj hello, thanks for opening the topic! I think it’s worth filing a bug report in this case, please open an issue under [GitHub - ansible/awx: AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.](https://github.com/ansible/awx) and put a link to it in this topic. Thanks