Managing user roles in an organization

In Gitpod, you can efficiently manage your organization by assigning different roles to users, ensuring each user has appropriate access and permissions to contribute effectively.

User roles

Gitpod supports various roles with different privileges to help structure your access. The Owner has critical access to organisation-level settings, such as inviting and managing other users. Members are typically trusted users within an organization. Collaborators are given limited access, which is useful when working with others who might be invited to work within your organization on a temporary or limited basis.

Permission Owner Member Collaborator
Manage Organization Users Yes No No
Edit Organization Settings Yes No No
Manage Organization Billing Yes No No
View Organization Usage Yes Yes No
Invite Organization Users Yes No No
View Organization Users Yes Yes No
Edit Repository Settings Yes Yes No
Edit Repository Variables Yes Yes No
Add Repositories Yes Yes No
Remove Repositories Yes Yes No
View Repositories Yes Yes No
View Branches Yes Yes No
View Prebuilds Yes Yes No
Trigger Prebuilds Yes Yes No
View Organization Settings Yes Yes No
Start Workspaces Yes Yes Yes

Add users to an organization

Once you create an organization you can invite users by using the unique invite URL from the Members page within an organization.

Change user permissions

New members will join with a Member role which you can later change if needed from the Members list using the more actions button. For more, see Roles.

Remove a user from an organization

You can remove an organization user from the Members list using the more actions button while hovering over the user entry.

Leaving an organization

You can leave an organization using the More Actions button in the Members list while hovering over your user entry.

Change default user role for new users

You can change the default role for new users who are invited or join an organization from the Organization settings page. By default, new users join with a Member role but you can change this to Collaborator instead.

Was this helpful?