The Codeberg Documentation website by The Codeberg Documentation Contributors is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
It bundles third-party font software licensed under a different license. Please look at the LICENSE file for details.
Changes to the original versions of the article as well as its individual authors can be looked up in this article's commit history
Codeberg and the Codeberg Logo are trademarks of Codeberg e.V.
An organization is a group of users that have access to a shared account. As such, they can all access the different repositories of the organization. An organization can be composed of several teams, each having a defined role in the project's development and also different access rights. This makes organizations an easy and powerful tool to collaborate on a project.
Everyone can create organizations on Codeberg for free. The following sections will show you how to create and manage an organization.
Details about the roles involved (owner, admin, member, etc) are given in the section Access rights below.
On your Dashboard, click on the
+ next to your avatar and select
In the new page, choose a name for your organization (here we choose
PolarClub) and select its visibility. Finally, choose what the administrators of repositories can do; if the box is ticked, repository administrators will be able to grant any team access to the repository (see Access rights below for details on repository administrators).
Confirm by clicking
You're now directed to the organization's dashboard.
On the dashboard, click on the avatar on the left and select the context (personal account or organization) you want to work with. Alternatively, switch between your repositories or your organizations tabs on the right side.
The organization's dashboard gives you an overview of the organization:
If you click on the
View [organization] (here
PolarClub, you'll be directed to the organization's page:
From here, you can access all repositories (there's currently none here) and create new ones. There's a list of all the members (
People) and teams; in this example, there is only one member (Knut the polar bear), and one team (
Owners) with one member (yourself) and no repositories.
The cog next to the organization's name will lead you to its settings:
This is where you can change general settings related to your organization, such as its name, avatar, website or visibility. You can also delete your organization, and access more advanced settings like organization webhooks:
Name of the organization is the name that will define the URLs of the organization and of all its repositories; it is recommended to keep it short. This name will also appear on the member's profiles (see People). On the other hand, the
Full Name is the name that will appear on the organization's home page.
Labels tab, you can create labels that will be used across all repositories of this organization. This will help with issues and pull requests. The default label set is a good starting point.
In the top right corner, you have access to the members and teams of your organization. These can also be accessed from the organization's page.
Teams tab gives you an overview of all the teams, their members and their number of repositories. You can also join a team from here if you have the permission to do so:
When you create an organization, a team
Owners is created and you are automatically added to this team. Members of the Owners' team have all permissions (see Access rights below for details).
+ New Team button to create a new team. Now, in the new page, you can set its name, permissions, and accessible repositories.
You can choose whether members of the team can only access some repositories explicitly added to the team, or whether they can access all repositories of the organization.
You can also allow members to be able to create new repositories on behalf of the organization.
If you have allowed repository administrators to grant or remove access for teams (see Create an Organization above), they can do so in the
Settings → Collaborators tab of the repository.
If you allow either
Write access, you can additionally set which sections of the repositories (code, issues, pull requests, releases and wiki) the members will have (read or write) access to. On the other hand,
Administrator Access automatically grants read and write access to all sections; this part of the page is hidden in this case.
See the section Access rights below for details.
If you belong to the team
Owners, you can edit teams. To do this, go to the
Teams tab and click on the team you want to edit:
Settings to edit the team as shown above for the creation of a team.
This is also where you can add or remove members to/from a team, and assign repositories to them.
People tab, you can get an overview of all the people who belong to your organization:
Somewhat counter-intuitively, this is not where you can add members; this is done in the
Teams tab (see Teams above). However, you can remove members from the
The visibility of the members can also be edited here;
Hidden means that the members' memberships will not be shown on their profiles, while
Visible makes the avatar of the organization appear in the info card on their profile, as shown in the screenshot below. Note that your membership will always be visible to you on your profile; this visibility setting is for other users only.
Shown here is also whether or not each member has activated two-factor authentication (2FA, see Setting up Two-factor Authentication).
Finally, from here you can choose to leave the organization.
An overview of the repository permissions is given in the article Repository Permissions.
Members of the "Owners" team can do everything that admins can do. However, only owners of the organization can manage the organization, which includes:
When owners allow members of a team to be able to create new repositories for the organization (see box "Create repositories" in Teams settings), the member who creates the repository will be added as a collaborator with administrator rights to this repository (see Invite Collaborators for details).
Hey there! 👋 Thank you for reading this article!
Is there something missing, or do you have an idea on how to improve the documentation? Do you want to write your own article?
For an introduction on contributing to Codeberg Documentation, please have a look at the Contributor FAQ.
© Codeberg Docs Contributors. See LICENSE