Skip to main content
An organization groups your repositories, registered public keys, and team members. You can belong to more than one organization. Each membership has its own role.

Join an organization

To join an existing organization, ask an admin to invite you. Follow the link in the invitation email to complete your account setup.

Create a new organization

Open the organization menu at the top of the dashboard sidebar. Select New organization… to start setup.
  1. Follow the steps to select a plan and choose an organization slug.
  2. Select a region if setup asks for one.
The person who creates the organization becomes an admin. New organization creation is not available in every environment. If you cannot see this option, contact support@pierre.co.

Switch organizations

Open the organization menu in the dashboard sidebar. Select the organization you want to use. The dashboard shows the repositories and settings for that organization.

Manage members

Only organization admins can open Settings → Members. From this page, admins can invite people and manage their membership. To invite someone:
  1. Select Invite user.
  2. Enter their email address.
  3. Select a role from the available roles.
  4. Select Invite.
The member list shows invitation status. Use a person’s menu to change their role, resend or revoke an invitation, or remove their membership. The menu shows the actions available for that person. An admin role grants access to member management and organization authentication settings.

Leave an organization

Open Settings. Select Leave in the Leave organization row and confirm. You lose dashboard access to that organization’s repositories and settings. The last admin cannot leave. Assign the admin role to another member first.

Access and repositories

Membership controls dashboard access. Applications authenticate with tokens signed by a private key whose public key is registered with the organization. See Authentication for key setup and token signing. Each Code Storage repository belongs to an organization. Use Storage Access & Permissions to choose repository claims, scopes, and ref policies for each client.

Service metadata

The Metadata API returns the cloud provider, region, and inbound IP addresses for the service that handles your organization’s Git and HTTP API requests. The request requires org:read. Use these addresses to configure firewall rules for Git and HTTP API access.