Organisations and teams

An organisation owns repositories the way a person does, at git.gitza.co.za/your-org/..., with one difference: nobody’s departure takes the code with them. Teams inside the organisation decide who may read, write to or administer which repositories.

Create an organisation

From the + menu choose New Organisation. The name becomes the address, so the same advice as for a username applies. Visibility controls whether the organisation’s page and its member list are public.

You become the first member of the Owners team, which can do anything in the organisation, including delete it.

Teams

A team is a named group of members with one set of permissions across a chosen set of repositories, or across all of them. Create teams under the organisation’s Teams tab. For each team you set:

• Repository access: specific repositories, or every repository the organisation owns, including ones created later.
• Permission: read, write, or administrator, per area. A team can be able to triage issues without being able to push, or push without being able to change settings.
• Repository creation: whether members of this team may create new repositories in the organisation.

A person can belong to several teams and gets the union of their permissions.

Members

Invite people under Members. Someone who is not yet on Gitza needs to create an account first; invite them by username. Removing a member from the organisation removes them from every team in it at once.

Move a repository into an organisation

A repository you own personally can be transferred under its Settings → Danger Zone → Transfer Ownership. The address changes to the organisation’s, and the old address redirects for clones and links until something else takes the name.

Next

The Team tier adds organisation-wide audit and export; see Plans and billing.