# Management of Namespace Owners in Galaxy **URL:** \ **Category:** Get Help\ **Tags:** galaxy-ng\ **Created:** [October 11, 2023, 3:29pm UTC](https://forum.ansible.com/t/management-of-namespace-owners-in-galaxy/1638 "2023-10-11T15:29:56Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![jholland](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@jholland](https://forum.ansible.com/u/jholland)\ **Post date:** [October 11, 2023, 3:29pm UTC](https://forum.ansible.com/t/management-of-namespace-owners-in-galaxy/1638/1 "2023-10-11T15:29:56Z")
It was mentioned in another post that: “in galaxy we’re managing namespace ownership directly via users”. How do we add/remove owners for our namespace? Is that documented somehere? Many thanks 🙂 ---
**Author:** ![IPvSean](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ipvsean/32/1153_2.png) [@IPvSean](https://forum.ansible.com/u/IPvSean)\ **Post date:** [October 11, 2023, 5:22pm UTC](https://forum.ansible.com/t/management-of-namespace-owners-in-galaxy/1638/2 "2023-10-11T17:22:43Z")
I think you would click on the left-hand menu `Collections` then click on `Namespaces` then click on `My namespaces` ![image](https://us1.discourse-cdn.com/ansible/original/2X/3/3e10ee4bade1b3e8a502116ca9cb645a6a10b749.png) Then click on `Access` and assign users there ---
**Author:** ![jholland](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@jholland](https://forum.ansible.com/u/jholland)\ **Post date:** [October 11, 2023, 5:54pm UTC](https://forum.ansible.com/t/management-of-namespace-owners-in-galaxy/1638/3 "2023-10-11T17:54:39Z")
Hi @IPvSean, seems reasonable, but there is only the option of groups: ![Screenshot 2023-10-11 at 18.52.47](https://us1.discourse-cdn.com/ansible/original/2X/0/0a10236a05d9ff079bedf862bbd4fd4146d5752f.png) And the list of groups is a list of totally random stuff: ![Screenshot 2023-10-11 at 18.52.54](https://us1.discourse-cdn.com/ansible/original/2X/4/465ed3f3ce0454751daa0e36a2010617a591fed1.png) With the “Filter by name” box I can’t find any of our users, the list seems totally unrelated to us? ---
**Author:** ![tannerjc](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/tannerjc/32/985_2.png) [@tannerjc](https://forum.ansible.com/u/tannerjc)\ **Post date:** [October 11, 2023, 6:29pm UTC](https://forum.ansible.com/t/management-of-namespace-owners-in-galaxy/1638/4 "2023-10-11T18:29:02Z")
Namespace management with users is a work in progress that is almost done [Allow users for namespace creation. by jctanner · Pull Request #1899 · ansible/galaxy\_ng · GitHub](https://github.com/ansible/galaxy_ng/pull/1899) For now, the only way to see and manipulate the owners of a v3 namespace are through the v1 “backdoor” as documented here [Administration - Galaxy NG](https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/community/administration/#validating-and-fixing-a-user-via-the-api) ---
**Author:** ![jholland](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@jholland](https://forum.ansible.com/u/jholland)\ **Post date:** [October 13, 2023, 10:41am UTC](https://forum.ansible.com/t/management-of-namespace-owners-in-galaxy/1638/5 "2023-10-13T10:41:56Z")
Thanks @tannerjc. I see the PR is merged, looking forward to the changes going live on [galaxy.ansible.com](http://galaxy.ansible.com) ---
**Author:** ![tannerjc](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/tannerjc/32/985_2.png) [@tannerjc](https://forum.ansible.com/u/tannerjc)\ **Post date:** [October 13, 2023, 1:06pm UTC](https://forum.ansible.com/t/management-of-namespace-owners-in-galaxy/1638/6 "2023-10-13T13:06:05Z")
We have the UI components deployed in galaxy-dev, but I found another bug in the API and have a fix in flight … [Enable social auth users to see other users. by jctanner · Pull Request #1934 · ansible/galaxy\_ng · GitHub](https://github.com/ansible/galaxy_ng/pull/1934) ---
**Author:** ![jholland](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@jholland](https://forum.ansible.com/u/jholland)\ **Post date:** [October 18, 2023, 2:55pm UTC](https://forum.ansible.com/t/management-of-namespace-owners-in-galaxy/1638/7 "2023-10-18T14:55:48Z")
Thank you, looks like the user-based approach is now live in prod 😁 Can I ask how the `groups` option works? How do we create/modify a group, is it meant to avoid listing individual users as namespace owners? Thank you ---
**Author:** ![tannerjc](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/tannerjc/32/985_2.png) [@tannerjc](https://forum.ansible.com/u/tannerjc)\ **Post date:** [October 18, 2023, 3:18pm UTC](https://forum.ansible.com/t/management-of-namespace-owners-in-galaxy/1638/8 "2023-10-18T15:18:01Z")
GalaxyNG’s RBAC up till now was group driven. An internal architecture decision was made to switch to user based RBAC for community galaxy so that we didn’t have tens of thousands of groups in the system. There’s nothing technically stopping the usage of groups still for RBAC, but we’d have to enable the group and user management components in the UI to make it more obvious and then also consider how we go about delegating permissions for group CRUD. I’d say that for the time being, just ignore the groups elements in that UX. If it’s something you’d like to have though, we can take that as a feature request. ---
**Author:** ![jholland](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@jholland](https://forum.ansible.com/u/jholland)\ **Post date:** [October 19, 2023, 8:29am UTC](https://forum.ansible.com/t/management-of-namespace-owners-in-galaxy/1638/9 "2023-10-19T08:29:04Z")
Understood, thanks for the detailed explanation. We’ll just do individual user-based CRUD for now. Given user auth is outsourced to GitHub, a natural extension would be to use teams defined within GitHub as the “groups”, that would work very well for us as the collection of users who need to be namespace owners are already in a GitHub team, but I admit I have no idea if this idea is technically feasible. Thank you