Organizations
Understand organizations in BlameTrail -- the top-level container for services, monitors, incidents, integrations, and team members.
Every BlameTrail account belongs to an organization. The organization is the top-level container that scopes all resources: services, monitors, incidents, deploys, integrations, and team members. All data within BlameTrail is isolated at the organization level.
Organization settings
Configure your organization by navigating to Organization > Settings. The following settings are available:
| Setting | Description |
|---|---|
| Name | The display name for your organization, shown in the sidebar and on dashboards. |
| Timezone | The timezone used for dashboard displays, schedule calculations, and timestamp formatting across the platform. |
Organization-level integrations
Integrations configured at the organization level apply to all services and members within the organization. Manage these from Organization > Integrations:
GitHub token
A GitHub personal access token or fine-grained token that enables deploy commit enrichment across all linked repositories. When configured, BlameTrail uses this token to fetch commit metadata, pull request details, and changed files for every deploy event.
See GitHub Token Setup for configuration details.
Slack
Connect a Slack workspace to receive incident notifications. BlameTrail sends alerts when incidents open and resolve, including the affected service, monitor, incident type, and top suspect deploy.
See Slack Integration for setup instructions.
Sentry
Link a Sentry organization to ingest Sentry issues as BlameTrail incidents. This provides a unified view of errors and outages in a single timeline.
See Sentry Overview for details.
Webhook endpoints
Register custom HTTP endpoints to receive structured event payloads for incidents and deploys. Useful for integrating BlameTrail with internal tools, PagerDuty, Datadog, or any system that accepts webhooks.
See Webhooks for payload formats and configuration.
Single Sign-On (SSO)
Organizations on the Enterprise plan can configure SSO/SAML so team members authenticate through a corporate identity provider such as Okta, Azure AD, or Google Workspace.
Configuring SSO
- Navigate to Settings > Organization.
- In the Single Sign-On card, click Configure SSO. This opens a setup portal where you can connect your identity provider.
- Follow the provider-specific instructions to complete the connection.
- Once the connection status shows active, your team can sign in via SSO from the login page.
SSO enforcement
After at least one admin has signed in via SSO, you can enforce SSO for all members of the organization. When enforcement is enabled, password-based login is blocked for users who belong to the organization — they must use the SSO flow instead.
To enable enforcement, click Enforce SSO in the Single Sign-On card. A confirmation dialog will appear. Enforcement can be disabled at any time by clicking Disable Enforcement.
If the SSO connection is deactivated or deleted by the identity provider, enforcement is automatically disabled to prevent lockout.
SSO login
Users sign in via SSO by clicking Sign in with SSO on the login page, entering their organization slug, and authenticating with the configured identity provider. New users are automatically provisioned and added to the organization on first login.
Creating an organization
An organization is created automatically when you sign up for BlameTrail. Each account belongs to exactly one organization. The user who creates the account is assigned the Owner role.
Switching context
All navigation, data, and settings in BlameTrail are scoped to your organization. There is no cross-organization data access. If you need to work with multiple organizations, sign in with separate accounts.
Next steps
- Members and Roles -- Invite team members and manage permissions.
- Plans and Pricing -- Understand the limits that apply to your organization.