# Access to namespace after galaxy-ng move

**URL:** <https://forum.ansible.com/t/access-to-namespace-after-galaxy-ng-move/1722>\
**Category:** Get Help\
**Tags:** galaxy-ng\
**Created:** [October 15, 2023, 2:44pm UTC](https://forum.ansible.com/t/access-to-namespace-after-galaxy-ng-move/1722 "2023-10-15T14:44:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dschier](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dschier/32/1634_2.png) [@dschier](https://forum.ansible.com/u/dschier)\
**Post date:** [October 15, 2023, 2:44pm UTC](https://forum.ansible.com/t/access-to-namespace-after-galaxy-ng-move/1722/1 "2023-10-15T14:44:32Z")

</div>

Hi all,

after the move to galaxy NG, two things happened. The first one is, that my GitHub handle is finally updated, which is super nice. The other one is, that I lost access to my collection namespace for whiletruedoio.

I would love to get the access back. Is there something you can help me with the same?

tl;dr:

My Galaxy/Github handle is: dschier-wtd  
I want to get access to the whiletrueodio namespace

Best,  
Daniel

---

<div class="post-metadata">

**Author:** ![dschier](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dschier/32/1634_2.png) [@dschier](https://forum.ansible.com/u/dschier)\
**Post date:** [November 25, 2023, 9:21am UTC](https://forum.ansible.com/t/access-to-namespace-after-galaxy-ng-move/1722/2 "2023-11-25T09:21:20Z")

</div>

Well, I don’t want to be pushy on this.

Is there any progress to grant access to my previous namespace? Do I have to re-request it in some way? It’s not that I am not willing to help, but I don’t know how to make things like his happen.

@gwmngilfen @felixfontein do you have any idea how to address this in a better way? ☹

---

<div class="post-metadata">

**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\
**Post date:** [November 27, 2023, 11:07am UTC](https://forum.ansible.com/t/access-to-namespace-after-galaxy-ng-move/1722/3 "2023-11-27T11:07:10Z")

</div>

Thanks for being polite, I think you’re being the right amount of pushy. I know the Galaxy team are still getting used to doing forum triage, I’ll poke them 😛

Thanks for your patience!

---

<div class="post-metadata">

**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:** [November 27, 2023, 9:22pm UTC](https://forum.ansible.com/t/access-to-namespace-after-galaxy-ng-move/1722/4 "2023-11-27T21:22:17Z")

</div>

Sorry, this one got lost in the pile of other threads.

I’ve added dschier-wtd as an owner of [whiletruedoio](https://galaxy.ansible.com/ui/namespaces/whiletruedoio/?tab=access)

---

<div class="post-metadata">

**Author:** ![dschier](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dschier/32/1634_2.png) [@dschier](https://forum.ansible.com/u/dschier)\
**Post date:** [November 28, 2023, 7:39pm UTC](https://forum.ansible.com/t/access-to-namespace-after-galaxy-ng-move/1722/5 "2023-11-28T19:39:49Z")

</div>

Thank you so much. This worked out perfectly fine. I am able to access the namespace again.

PS: There is no need to be sorry. It is fully understandable that this release was putting a lot of pressure on you guys and things might get lost.