Hub admin permissions

Release date: 24th January 2024

With this release, once a user has been given hub admin permissions, they can set permissions for that hub and its child repositories.

This feature is useful if you have multiple hubs that are managed independently from each other. For example, if you have a hub per brand, you may prefer having hub admins who manage their own hubs rather than having multiple organization admins, who can see and manage permissions across all hubs and repositories. An added benefit of hub admins being able to manage permissions is that it can help to alleviate you organization admin from routine tasks.

Note, the organization admin can assign the hub admin role to any user.

For information about the different roles and what they allow users to do, see Roles.

New for the hub admin role
Link copied!

In addition to the actions that hub admins could already perform, such as managing repositories, and all the actions performed by other hub roles, they can now:

Set permissions for the hubs (and their repositories) for which they are admins. See Assigning hub and repository roles
Create teams and use them to set permissions. Note, hub admin users can't update or delete teams that other organization admins or hub admins have created. See Creating teams

For information about what actions hub admin users can do, see the hub admin role.

Identifying hub admins
Link copied!

In account management, a new "Hub Admin" icon makes it easy to see who is assigned the hub admin role. If you have the hub admin role for at least one hub, the "Hub Admin" icon is displayed at the top right of the window.

All users who are assigned the hub admin role, are identified with the "Hub Admin" icon on the Members tab.

New hub admin permissions