Organizations and projects

An organization is the account, membership, plan, and billing boundary. A project groups the resources and checks for one validation boundary.

Choose project boundaries

Each source, secret metadata entry, schedule, notification channel, API key, project worker, check, and report belongs to a project. A project worker connects to one project.

Create separate projects to group and separate:

• worker infrastructure or Kubernetes Secrets
• backup sources and schedules
• checks and reports
• project-scoped API keys

Organization membership grants access across that organization's projects according to the member's role. Separate projects do not create separate human membership lists. Use separate organizations when teams require different membership boundaries.

Avoid creating projects only to label similar schedules; clear names and descriptions are usually enough when the same team and worker boundary applies.

Create a project

1. 1

   Open the organization

   Select the intended organization in the console. Confirm that its current plan has available project capacity.

2. 2

   Create and name the project

   Choose a stable name that identifies the system, environment, or responsibility being validated. Add a description so members know which backups and workers belong there.

3. 3

   Add project resources

   Create a project worker, secret metadata, source, and schedule. The console's active-project selector determines where a new resource is created.

Manage access

Organization members inherit their role across all projects in the organization. Viewer is read-only; Editor, Technical admin, and Owner can manage project resources. Only owners manage billing, and owner membership has additional restrictions.

Use team roles for people and project-scoped API keys for automation. Do not share a person's session or a single broad API key across unrelated projects.