Supported Logins

Breakdown Takedown provides flexible authentication options for individuals, teams, and enterprise organizations, supporting leading identity providers, modern federation standards, domain-level routing, and multi-factor authentication.

Supported identity providers & login methods

We support a wide range of authentication methods and enterprise identity protocols to fit any team’s security and compliance needs:

• SSO (Single Sign-On) — Centralized authentication enabling seamless employee access through your organization’s identity provider.
• OIDC (OpenID Connect / ODIC) — Modern identity federation built on OAuth 2.0 for standard-compliant single sign-on.
• Google — Fast and secure authentication using Google accounts and Google Workspace via Google Cloud Identity Platform (GCIP).
• Microsoft — Sign in using personal Microsoft accounts, Office 365, Azure Active Directory, and Microsoft Entra ID.
• SAML 2.0 — Enterprise identity federation compatible with Okta, Ping Identity, OneLogin, Microsoft Entra, and custom SAML IdPs.
• GitHub — Convenient developer authentication with your personal or organizational GitHub account.
• Email & Password — Direct credential-based authentication for users who prefer standard email sign-in.

Logging in via the general domain

The primary application domain (https://breakdowntakedown.com or https://app.breakdowntakedown.com) serves as the universal entry point for all users:

• Standard login screen — Tap "Log in" on the navigation bar to sign in with Google or your preferred credential provider.
• Workspace lookup — Enter your company name or organization slug in the workspace lookup field to jump directly to your organization’s dedicated sign-in portal.
• Multi-organization access — Users who belong to multiple organizations can authenticate once on the general domain and switch between organizations from the dashboard.

Logging in via enterprise subdomains

For enterprise teams with custom identity provider configurations, Breakdown Takedown supports dedicated enterprise subdomains (such as https://your-company.breakdowntakedown.com):

• Automatic tenant resolution — Accessing your organization’s custom subdomain automatically detects your workspace settings and loads your team’s custom branding.
• Custom identity provider button — The login interface renders a dedicated button tailored to your company’s IdP, such as "Sign in with SSO", "Sign in with Microsoft", or custom SAML.
• Direct authentication — Clicking the branded button routes directly to your enterprise identity provider without requiring users to type their domain or search for their provider.
• URL query parameter fallback — Teams can also reach their customized tenant login experience on the primary domain by appending ?org=<slug> or ?subdomain=<slug> (e.g., https://breakdowntakedown.com/?org=your-company).
• Automatic role provisioning — Authenticated users are mapped directly into your organization with their assigned team permissions.

Enabling Multi-Factor Authentication (MFA)

Multi-Factor Authentication (MFA) adds a critical layer of defense by requiring two or more verification factors before granting access. MFA can be enabled and enforced across all supported login methods:

• Google accounts — Users can turn on 2-Step Verification in their Google Account security settings (using Google Authenticator, phone prompts, or security keys). Google Workspace administrators can enforce mandatory 2-Step Verification across all organization accounts.
• Microsoft / Entra ID — Users can configure multi-factor authentication via the Microsoft Authenticator app, SMS codes, or FIDO2 hardware keys. IT administrators can enforce tenant-wide Conditional Access MFA policies.
• Enterprise SAML 2.0 & OIDC — Organizations using SAML 2.0 or OIDC (such as Okta, Ping Identity, or Azure AD) can enforce MFA policies directly at the IdP level. Users authenticating via their enterprise subdomain must pass their IdP’s MFA challenge before receiving an access assertion.
• GitHub accounts — Users can enable two-factor authentication (2FA) in GitHub Account Settings using TOTP authenticator apps or hardware security keys. GitHub organization owners can also mandate 2FA for all organization members.
• Email & Password accounts — For direct password accounts, time-based one-time password (TOTP) MFA can be enabled using authenticator apps such as Google Authenticator, Authy, or 1Password.