{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidtg43tb2kbrm53iqevt4khblbr5avl3wdm4kuydqeog6cvvt5vqy",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mk5qdqrx7pj2"
  },
  "path": "/t/how-to-use-gated-user-access-or-suitable-other-functionality-for-user-access-within-an-organization/175405#post_4",
  "publishedAt": "2026-04-23T08:54:27.000Z",
  "site": "https://discuss.huggingface.co",
  "textContent": "TLDR: Having “member-group” concept where an org-admin can add/remove some set of users would make member access via Resource Group much easier.\n\nOn emailing the team-support email id mentioned above, I got their inputs quite fast. Based on that, it seems I could recommend making a new Resource Group for this, then move the repo “SpecialModel” to the new RG. Then we would add all the existing members of the original RG to the new RG + the person for whom we wanted to grant access newly.\nThis would work, but I see no concept of “member-groups” in HF. If such a thing existed then it would be much easier to map all necessary members in to any new Resource Groups. I would just select such the existing member-group for “Finance” and have to add just the one new person. Futher, if if Person-3 left the Finance department some day, I could easily edit the “member-group” for Finance to remove Person-3. And the members who are then mapped to one or more RG’s using this member-group is updated automatically. But right now, I would need to every resource group created and delete Person-3 from them.",
  "title": "How to use Gated User Access (or suitable other functionality) for user access within an Organization?"
}