# Can we add access restrictions to your groupID

**URL:** <https://community.sonatype.com/t/can-we-add-access-restrictions-to-your-groupid/6977>\
**Category:** Sonatype Nexus Repository\
**Created:** [July 22, 2021, 5:10am UTC](https://community.sonatype.com/t/can-we-add-access-restrictions-to-your-groupid/6977 "2021-07-22T05:10:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sharathks84](https://avatars.discourse-cdn.com/v4/letter/s/db5fbb/32.png) [@sharathks84](https://community.sonatype.com/u/sharathks84)\
**Post date:** [July 22, 2021, 5:10am UTC](https://community.sonatype.com/t/can-we-add-access-restrictions-to-your-groupid/6977/1 "2021-07-22T05:10:38Z")

</div>

I am new to repository hosting in opnesource hosting.  
How can i make sure only i have access for this groupID hosting and avoid other members to publish artifacts in my domain space

---

<div class="post-metadata">

**Author:** ![dsawa](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/dsawa/32/729_2.png) [@dsawa](https://community.sonatype.com/u/dsawa)\
**Post date:** [July 22, 2021, 6:29am UTC](https://community.sonatype.com/t/can-we-add-access-restrictions-to-your-groupid/6977/2 "2021-07-22T06:29:28Z")

</div>

Hi Sharath, in your case Content Selectors are your friends. You will need to create appropriate Content Selectors, then create Privilege with your Content Selector, then assign it to a role and apply the role on appropriate users. You can find more about Content Selectors in the documentation: [Content Selectors](https://help.sonatype.com/repomanager3/system-configuration/access-control/content-selectors)

---

<div class="post-metadata">

**Author:** ![mmartz](https://avatars.discourse-cdn.com/v4/letter/m/e9bcb4/32.png) [@mmartz](https://community.sonatype.com/u/mmartz)\
**Post date:** [July 22, 2021, 3:02pm UTC](https://community.sonatype.com/t/can-we-add-access-restrictions-to-your-groupid/6977/3 "2021-07-22T15:02:50Z")

</div>

Depending on your use-case it may be simpler to use a group repository and provide appropriate permissions to only allow pushing to certain hosted members in the group. It won’t protect the namespace though, if you need to protect the namespace you need to use the content selector feature.