In Ansible Tower 3.5.x and later versions, when users are added to a team, there is no UI component/option to set users as team admin. However, calling API could still assign users with team admin roles (POST /api/v2/users/id/roles/).
Is there any option to assign user with team admin role via UI? Is the team admin role deprecated?
When adding the user, it should be an option to add a user with the team admin role.
No option to add a user with the team admin role
In the official user guide of Ansible Tower 3.5.x and later versions (https://docs.ansible.com/ansible-tower/latest/html/userguide/teams.html#add-a-user), the example picture doesn't show there is an option to add a user with team admin roles.
However, in earlier docs (https://docs.ansible.com/ansible-tower/3.4.1/html/userguide/teams.html#add-a-user), the example picture still had that option
It's an option, but team admin only lets you add/remove users from the team. Is this a permission you need to use in practice outside of the org admin doing it?
@wenottingham We had the option to add a user to team as team admin via UI. Now it is removed without mentioned in the release note (or perhaps I missed it). Some of our tower users asked about the change (they cannot add team admin), which is why I submit this request.
If this change is desired, could we know the consideration behind this change?
Mostly just that it's not a useful permission in practice. We had more confusion by users who thought it provided org-admin like privileges at a team level.
I'd like to reopen such discussions.
Having USER/ADMIN permissions at a team level allows using Teams for self-service user management. i.e. this permits us handing over user management to just a small group of admins.
Perhaps this role can be named "TEAM ADMIN" to avoid confusion.
We needed self-service user management for some automation automation we built on top of Tower. Lacking this feature in Tower we had to hook up a rather ugly system that in our case pulled users dynamically from an LDAP group (internally: Rover) and add/remove these users individually from Tower assets (like a template). This was because our LDAP-backed system has this USER/ADMIN model while Tower teams do not. Admins still need to access an external UI to perform this user management.
@fpob
Most helpful comment
I'd like to reopen such discussions.
Having USER/ADMIN permissions at a team level allows using Teams for self-service user management. i.e. this permits us handing over user management to just a small group of admins.
Perhaps this role can be named "TEAM ADMIN" to avoid confusion.
We needed self-service user management for some automation automation we built on top of Tower. Lacking this feature in Tower we had to hook up a rather ugly system that in our case pulled users dynamically from an LDAP group (internally: Rover) and add/remove these users individually from Tower assets (like a template). This was because our LDAP-backed system has this USER/ADMIN model while Tower teams do not. Admins still need to access an external UI to perform this user management.
@fpob