GitHub Community
Setting Member Privilege for team creation in orgs via API #24712
-
|
Hey, I’ve looked through a few parts of the docs, but it looks like the setting to restrict Member Team Privileges via the orgs endpoint in the REST API. There are other internal member privileges that are supported, but not this one. There doesn’t appear to be a preview to enable it either, which I’ve used a few times in the past. Is this a gap that is planned to be covered in the near future, or is this setting intended to only be set manually via the UI? Setting in question: Setting team creation permissions in your organization - GitHub Docs Current org endpoint def: Organizations - GitHub Docs |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
Hey @autumnfound 👋 Thanks so much for your post and for joining the Community! I do see what you mean. Currently, there is no way to toggle the allow/disallow Teams creation for Org members via the API. I also know that over on the Enterprise side, a number of customers have requested similar, and have been added to an internal request thread. If you are a member of a GHE/S Organization, I might recommend opening a support ticket with them, directly: enterprise.github.com Support - GitHub EnterpriseThe power of GitHub's social coding for your own workgroup. Pricing, tour and more. If you’re a non-Enterprise user, I highly recommend submitting via this feedback form: Share feedback - GitHub Support//support.github.com/contact/feedback …to add your +1 for this to be added to either REST or GraphQL, or both! Thanks again for bringing this up. 🙇 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for getting back (and sorry for late response lol!), I know we have licensing/product arrangements w/ Github, but I don’t know if we qualify as Enterprise. I’ll let my team know and we’ll hit on the solution given. I’ve marked your answer as solution as there is no current endpoint for this. I’d probably give my +1 to REST as that’s what we use internally for our binding! |
Beta Was this translation helpful? Give feedback.
-
|
I’ve been asked by my team to follow up and I figure this is the least intrusive way to do so! We’ve been getting some pushes in the Eclipse community about changing groups to “public” from “secret”, and managing this setting is the only blocker to this currently (574879 – GitHub Mirror for Scout removed?). Is there any public resource I can follow on this issue in the future to point them at to reduce pings and other such things? Thanks in advance! |
Beta Was this translation helpful? Give feedback.
Hey @autumnfound 👋
Thanks so much for your post and for joining the Community!
I do see what you mean. Currently, there is no way to toggle the allow/disallow Teams creation for Org members via the API.
I also know that over on the Enterprise side, a number of customers have requested similar, and have been added to an internal request thread. If you are a member of a GHE/S Organization, I might recommend opening a support ticket with them, directly:
enterprise.github.comSupport - GitHub Enterprise
The power of GitHub's social coding for your own workgroup. Pricing, tour and more.
If you’re a non-Enterprise user, I highly recommend submitting via this feedback form:
support.github.com