You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you are an admin of the organization, you can create and manage Resource Groups from that page.
36
+
Organization admins can create and manage Resource Groups from that page. Depending on the organization's settings, members with lower roles may also be allowed to create resource groups (see [Who can create resource groups](#who-can-create-resource-groups) below).
37
37
38
38
After creating a resource group and giving it a meaningful name, you can start adding repositories and users to it.
39
39
@@ -52,6 +52,18 @@ Remember that a repository can be part of only one Resource Group. You'll be war
By default, only organization admins can create new resource groups. Org admins can change this by setting the **minimum member role required to create resource groups** on the resource groups settings page.
58
+
59
+
The available options are:
60
+
-**Admins only** (default) — only org admins can create resource groups.
61
+
-**Write** — members with Write or Admin role can create resource groups.
62
+
-**Contributor** — members with Contributor, Write, or Admin role can create resource groups.
63
+
-**All members** — any org member can create resource groups.
64
+
65
+
When a non-admin member creates a resource group, they are automatically added as an **admin** of that newly created group. When creating a resource group via the API, non-admin creators must include at least one admin in the group's initial user list.
66
+
55
67
## Resource Groups API
56
68
57
69
You can list resource groups and add users to them (or change a member's org role and resource group assignments) via the Hub API. For the full reference, examples, and batch workflows, see the [Programmatic User Access Control Management](./programmatic-user-access-control) guide.
0 commit comments