Organizations in Probo.CI

A Probo.CI Organization is the top-level grouping that ties together your repositories, projects, builds, team members, and billing. Understanding how organizations fit into the Probo data model helps you manage access, track usage, and make sense of your subscription limits.

1. What Is an Organization

   When you enable an organization in Probo.CI for the first time, a Probo Organization is automatically created to represent the git hosting provider account that owns it - whether that is a GitHub organization, a Bitbucket workspace, a GitLab group, or a personal user account. From that point on, all repositories from that provider account are grouped under the same Probo Organization.

   An Organization has a name, a set of linked provider accounts, a subscription, and a team of admins.

2. The Organization Hierarchy

   Organizations sit at the top of a three-level hierarchy:

   • Organization - owns all repositories from one or more provider accounts, holds the subscription and billing details, and tracks usage across all projects.
   • Project - corresponds one-to-one with an enabled repository. A project belongs to exactly one organization.
   • Build - a single build environment created for a pull request. Builds belong to a project, and through it, to an organization.

   
   

   All disc usage, concurrent build limits, and subscription quotas are measured and enforced at the organization level, not the project or build level.

3. Team Members and Roles

   Access to a Probo Organization works at two levels:

   3.1 Organization Admins. Admins are explicitly added to an organization and can manage organization-wide settings: who the admins are, the subscription tier, the payment method, and billing history. A user can be an admin of multiple organizations.

   3.2 Project Collaborators. Any user who has access to a repository at the provider level (GitHub, Bitbucket, etc.) and has a Probo.CI account automatically gains access to that repository’s Probo Project. Collaborators can view builds and perform build operations such as pinning, rebuilding, and deleting - but cannot manage organization settings.

   Users can belong to multiple organizations simultaneously, either as admins, as collaborators, or both.

4. What an Organization Controls

   Through its subscription, an organization governs the following limits across all of its projects and builds:

   Setting	Description
   Disc Space	How much disc space is available for completed builds across all Projects
   CPU Limits	The number of processors available to each build
   Memory Limits	The amount of memory available to each build
   Concurrent builds	How many builds the organization can run simultaneously

   See the Quotas and Build Queue documentation for details on how these limits are enforced.

5. How Organizations Are Created

   Organizations are created automatically when activated - no manual setup is required. It also assigns the enabling user as its first admin. Subsequent repositories from the same provider account become projects within that organization and are linked to the existing organization automatically when they are enabled.

6. Questions

   If you have questions about your organization’s settings, team membership, or subscription limits, please reach out to us at hello@probo.ci.