Top-level entities on the Scrums.com platform. Organizations own workspaces, hold subscriptions, and are the root scope for all billing and access control.
The Scrums.com API is planned and not yet publicly available. Endpoints and behaviour are subject to change before release.
An organization (ORG-*) is the top-level entity on the Scrums.com platform. It represents a company or enterprise customer. All workspaces, subscriptions, billing, and platform-level governance are scoped to an organization.The organization is the commercial entity: it holds a Plan, activates Subscriptions, and receives Invoices. Every Service Line active on the platform traces back to an organization.
An organization can own multiple workspaces. Each workspace is an independent operational unit with its own members, integrations, and Service Lines. Organizations provide the commercial and governance envelope; workspaces provide the operational context.
The organization’s active Plan determines which Service Lines can be activated across its workspaces. Subscriptions are held at the organization level and apply to all workspaces unless workspace-scoped subscriptions are configured.
Organization-level membership grants access across all workspaces within the org. Roles at the organization level are: owner, admin, billing, viewer. Workspace-specific roles are managed via Users & Roles.
One organization per company. Multiple workspaces within one organization provide the operational separation needed for teams and divisions. Creating multiple organizations for the same company complicates billing, cross-workspace visibility, and governance.
Set billing_email explicitly. Invoice delivery depends on this field. Ensure it reaches a team that can action payment rather than a personal inbox.
Apply settings before inviting users. Configure enforce_sso and require_mfa before adding members, so new users join under the correct security posture from the start.