Organizations
Create an organization, understand member roles, invite people, manage Team seats and teams, and turn organization capabilities on or off.
An organization is an account that owns repositories and groups people. Its login shares one
namespace with usernames, so gitdb.co/<login> is either a person or an organization, never both.
Your own username is a personal namespace, not an organization: individual plans (Free, Pro, Max, Ultra) are single-user.
Create an organization
- Click New in the top bar and choose New organization.
- On Create a new organization ("An organization owns repositories and lets your team
collaborate. You will be its owner."), fill in:
- Organization login: "This is the URL name (gitdb.co/
<login>) and shares the global namespace with usernames." It follows the same rules as a username: 4 to 39 characters; lowercase letters, digits, and hyphens; starts with a letter or digit; doesn't end with a hyphen; no two hyphens in a row; not taken by any user or organization; not reserved. - Display name
- Organization login: "This is the URL name (gitdb.co/
- Click Create organization →.
You become the organization's owner. Buying the Team plan also creates an organization for the team as part of checkout.
The organization page
gitdb.co/<org> shows the organization's display name and login, how many repos and members
it has, and its REPOSITORIES. Owners and admins also see a Settings button.
The New repository → link on this page opens the standard Create a new repository form, whose Owner is always your own username. The web form doesn't create repositories inside an organization.
Roles
Every member of an organization has one of four roles:
| Role | What it adds |
|---|---|
| owner | Everything an admin can do, plus the owner-only pages: Enterprise settings (organization capabilities) and Members (invitations, roles, removals, Team seats). |
| admin | Merges pull requests; manages Teams and organization-wide Read access; views the organization Audit log; sees each repository's Access control and Audit log settings. Always keeps full read access, and bypasses branch protection unless a rule has Enforce rules on administrators checked. |
| member | Works on the organization's repositories: reads and makes changes, opens and reviews pull requests. Subject to branch protection and read access rules. Can't merge pull requests. |
| readonly | Reads the organization's repositories. Write actions on gitdb.co and through GitDB's tools are refused, for example opening, reviewing, or commenting on pull requests, and a readonly member can't start AST indexing. Subject to read access rules. |
Members and invitations
Owners manage people in Settings → Members ("Manage who belongs to <org> and invite new people by
email").
- Invite a member: enter an email address, pick a role (owner, admin, member, or readonly), and click Invite.
- Members: change a member's role with the drop-down, or remove them with the delete icon.
- Pending invitations: each shows the email, role, when it was sent, and when it expires. Click Revoke to cancel one.
Invitations are available on Team and Enterprise accounts, and an owner has to turn on Member invitations in Enterprise settings first. On other accounts the page explains: "Member invitations are available on Team and Enterprise accounts. Individual plans (Free/Pro/Max/Ultra) are single-user."
Accepting an invitation
The invited person opens the link from the invitation email. They must be signed in: if they aren't, they're sent to the sign-in page and brought back to the invitation afterwards. People without a gitdb.co account create one first, then open the link again. Their verified email address must match the address the invitation was sent to. The page reads Join (organization) and "You've been invited to join the (organization) organization on gitdb.co." Clicking Accept invitation adds them to the organization and opens its page.
Team seats
On a Team organization, Settings → Members also shows Seats (in use / purchased). Members and pending invitations both take a seat.
To buy or release seats, enter a new Total seats and click Update seats. "Extra seats are $100/month each, prorated." You can't go below the seats already in use, or below the 5-seat plan minimum.
If the Team subscription has a problem, the page says so at the top:
- "Payment failed — update your card to keep this team active."
- "This subscription has ended. Resubscribe to restore team seats."
Teams
A team is a named group of organization members. Teams are used to grant or deny read access to specific paths. Owners and admins manage them in Settings → Teams.
- Under Create a team, enter a name and click Create.
- Click the team's name in the list to open it.
- Choose someone from Add an org member… and click Add. Only people who are already members of the organization can be added; a team never makes someone a member of the organization.
- Remove someone from the team with the delete icon next to their name. Delete a whole team with the delete icon in the team list.
Enterprise settings
The organization owner turns organization-wide capabilities on and off in Settings → Enterprise
settings ("Turn enterprise capabilities on or off for everyone in <org>"). Each capability has an
Enable / Disable button:
| Capability | What it does |
|---|---|
| Enterprise Audit | "Record a per-file audit trail of every member's reads and writes, and detect bulk-read anomalies." See Audit logs. |
| File / Code Access Control | "Enforce per-path read-ACL deny rules so restricted members cannot read protected files or code." See Access control. |
| Require two-factor authentication | "Every member who signs in with email + password must enter an emailed one-time code." Available on all plans. See Security and 2FA. |
| Automatic AST indexing | Index every push to this organization's repositories. See AST indexing. |
| Member invitations | Lets owners invite members by email. Team and Enterprise only; on Team, the number of invitable seats is the number you bought. |
A capability only works when your plan includes it and it's enabled here. If your plan doesn't include it, the row says "Not included in your current plan — contact sales to enable it." and it can't be enabled. Disabling is always possible. If the organization belongs to an enterprise that enforces a policy, the matching capability stays on.