administration/organizations.md

Organization settings

Group repositories and manage membership

An organization groups repositories under one name. Its settings control the organization title, description, and membership.

Organization role — A permission level for the organization settings: Owner, Admin, or Member.

Repository policy — The rules in a repository's nerudo.toml file. These rules control repository membership, approval keys, and approval requirements.

Organization roles and repository policy are separate. An organization role does not give private code access or replace repository approval rights.

Create an organization

Complete your Nerudo username setup before you make an organization. A temporary signup name cannot own a new organization.

Sign-in confirmation lasts five minutes. The creation page has controls to confirm your sign-in with a connected provider or passkey.

1. Open Create organization.
2. If Nerudo requests a username, select Choose your username.
3. Confirm your sign-in with a connected sign-in method.
4. Enter an available name in Organization name.
5. Enter a title in Organization title, if necessary.
6. Enter a description in Description, if necessary.
7. Select Create organization.

The name uses 1–39 lowercase letters, digits, or hyphens. It starts with a letter or digit.

The title has a maximum of 100 characters. The description has a maximum of 300 characters. Each field uses one line.

Nerudo makes the organization and gives your account the Owner role. The organization name becomes part of its address.

Organization creation does not move existing repositories or change repository policy.

Open organization settings

OWNER is a placeholder for the organization name. General settings use /OWNER/settings/general.

1. Open Profile settings.
2. Under Organizations, select your organization.
3. Select General, Members, Governance, or Developer access.

This list includes your memberships in organizations with no repositories. For an existing organization that requires operator setup, open its public page and select Settings.

An owner or admin can manage the organization settings. A member can examine their membership and leave the organization.

Change the title or description

1. Open General.
2. Confirm your sign-in if the previous confirmation has expired.
3. Change Organization title, if necessary.
4. Change Description, if necessary.
5. Select Save settings.

The page shows the saved title and description. This form does not change the organization name or its address.

Understand organization roles

Only an owner can give the Owner and Admin roles. The organization must keep at least one owner with an active account.

Organization owners and admins can manage repository descriptions, visibility, and transfers where permitted. Users still must have repository permission to read private code.

Add an existing user

The user must already have a Nerudo account and a completed username. Owners and admins can find users by Nerudo username.

Account ID — The stable identifier of a Nerudo account. Nerudo compares the username and Account ID with its account records when you save membership.

1. Open Members.
2. Confirm your sign-in if necessary.
3. Enter the person's username in Nerudo username.
4. Select Find user.
5. Make sure that Confirm this account shows the correct user.
6. Select the necessary Role.
7. Select Add member.

The user appears in the organization member list. This membership does not add their key or role to a repository's nerudo.toml.

Change or remove membership

An owner can change a listed user's role. An admin can remove ordinary members.

1. Open Members.
2. Find the user in Organization members.
3. Select a different Role, if necessary.
4. Select Save role.

To remove a permitted member:

1. Find the user in Organization members.
2. Select Remove member.
3. Confirm the removal.

The member loses their organization role. Repository roles in nerudo.toml stay in place until a separate policy change removes them.

Leave an organization

1. Open Members.
2. Find your membership.
3. Select Leave organization.
4. Confirm the action.

Your organization membership ends. Your account and repository policy roles stay in place.

The final active owner cannot leave. Before that owner leaves, another active account must have the Owner role.

Existing organizations without an owner role

Some organizations require operator setup before personal management is available. Repository approver roles do not automatically become organization owner roles.

An operator must explicitly assign the first organization owner. The operator checks the intended account and records the reason.

If the page requests operator setup, ask the Nerudo operator to review organization ownership. A new organization cannot use a name that already exists.

Governance and developer access

Governance links to each repository's policy settings. Each repository keeps its own nerudo.toml approval rules.

Developer access links to repository credential settings. Each credential belongs to a user; there is no shared organization sign-in identity.

Permanent organization deletion is not available in these settings.

Related guides

• Repository settings
• Developer access
• Signing keys
• Data and deletion
• Technical terms