Organizations

Organizations are a firm boundary between repository estates, administrators, policy decisions, tasks, reporting and billing.

An organization contains its users, code providers, repositories, teams, routines, policies, reports, tasks, API keys, webhooks, and billing state. Those resources are not shared with another BIMP organization.

Create an organization

Choose Create organization, enter the customer-facing name, and complete onboarding. BIMP keeps an incomplete organization in onboarding until an owner finishes or explicitly skips the remaining setup.

Use a name that you can distinguish in the organization switcher. Avoid names based only on an internal account number.

Switch organizations

Use the organization switcher in the application header. The active organization controls the repositories, policy, reports, and settings loaded by the application.

Users can be added to more than one Organization and they can have different permissions configured per Organization.

If a resource appears to be missing, be sure to confirm the active organization before creating it again.

Decide when to use more than one

Use separate organizations when you need a firm boundary between repository estates, administrators, policy decisions, tasks, or reporting. For example, a regulated business unit may need separate ownership and review controls from the rest of the software estate.

A separate organization is an isolation choice, not a certification claim. Avoid splitting one operating group without a clear ownership or policy reason; policy, reports, provider connections, and capacity are organization-scoped.

Update an organization

If you are an Owner, you can rename the organization from Settings → Organization → Admin. Review defaults after an ownership or operating-model change because routines, notifications, and remediation settings affect later repository work.

Billing boundary

Billing and licensed capacity are organization-scoped. Each organization shows its own edition, repository usage, artifact usage, renewal state, and management actions under Settings → Organization → Billing and usage.

For current editions and capacity, see BIMP Editions.

Delete an organization

Deletion removes the organization’s BIMP resources and access. It does not delete the connected GitHub or GitLab account, but provider requests or installations may require separate provider-side review.

Open Settings → Organization → Admin. Before deletion:

1. Open the deletion preview.
2. Review the resources that will be removed.
3. Export or retain any evidence your organization requires.
4. Confirm that another organization does not depend on a process documented only in the organization being deleted.

Only continue when the preview matches your intent. If deletion is unavailable, confirm that you are an Owner and that the organization is not already in a restricted lifecycle state.