/settings/sso) in the environment you want to configure. You need organization settings management permission. Configuration belongs to your active organization; switch organizations before configuring another team.
Before you start
Have these items ready:- Access to your email domain’s DNS records.
- Administrator access to your identity provider.
- An existing Forecastable account in your organization for testing.
- A working native password account for emergency access if you plan to require SSO.
Step 1: Verify your domain
- Enter the part after
@in your team’s work emails, such asexample.com. Enter a domain, not an email address, website URL, or wildcard. - Click Get DNS record.
- Add the displayed TXT record in your DNS provider. Use the copy buttons beside the record type, name, and value.
- Click Verify example.com after the record is publicly visible.
- Click Continue to identity provider.
Some DNS providers automatically append your domain. If yours does, enter
_forecastable-sso as the host rather than adding the domain twice. Copy the actual challenge value from Forecastable; sample values do not verify ownership.
DNS changes can take time to appear. A challenge expires after seven days; use Generate new record and replace the TXT value if it expires. A domain assigned to another Forecastable organization cannot be claimed. Verify each email domain separately: verifying example.com does not verify sales.example.com.
Domain verification proves that your organization controls the domain. It does not prove that a particular person owns an email address. Your identity trust policy determines how Forecastable trusts each person’s address.
Step 2: Connect your identity provider
Create an application for Forecastable in your provider. Restrict it to the intended users or groups. Configure password requirements, MFA, and other identity checks in the provider.OpenID Connect
Select OpenID Connect (OIDC) and use a confidential web application with authorization-code flow. Enableopenid, email, and profile scopes.
The issuer URL is not the redirect URI. For example, an Authentik issuer may be
https://auth.example.com/application/o/forecastable/. Its discovery document is usually beneath that issuer at .well-known/openid-configuration; enter the document’s issuer value rather than the discovery document URL.
The redirect URI points to Forecastable’s Cognito federation endpoint. Its hostname depends on the environment and may use an AWS Cognito domain or a configured Forecastable custom domain. Always copy the address shown in the environment’s SSO settings. Do not substitute the Forecastable login page or /login/cognito/return.
SAML 2.0
Select SAML 2.0 and create a SAML application in your provider.
Start sign-in from Forecastable. Unsolicited provider-initiated callbacks do not have the browser-bound sign-in transaction and are rejected.
User details
Your provider sends named fields describing each person. OIDC calls them claims; SAML usually calls them attributes. Enter the field names, not a person’s actual email or name.
OIDC defaults are filled in under User details. Change them only when your provider uses different names. For SAML, use the complete attribute name, including a URL prefix if the provider uses one. Keep the email verification field mapping configured even when using company-managed identities; this allows you to select Verified email later without forgetting the mapping.
Check and connect
- Click Check settings to inspect the provider and shared Cognito client configuration.
- Review any reported changes. A check is a configuration preview, not a successful user sign-in test.
- Click Connect identity provider and confirm.
- Forecastable switches to the management area after the connection succeeds.
Manage your connection
The management area contains Sign-in policy, Identity provider, and Domains tabs.Share a company sign-in link
After connecting your provider, use Company sign-in link above the management tabs:- Review the Sign-in address suggested from your organization name, or enter your own.
- Click Create link. Addresses must be unique in this environment and contain 3–63 letters, numbers, or hyphens, starting and ending with a letter or number. Reserved names such as
google,sso, andlogoutare unavailable. Letters are saved in lowercase. - Copy the saved Sign-in link, for example
https://app.forecastable.com/login/acme. Use the exact hostname shown in your environment. - Click Test sign-in link to open it in a new tab. It goes directly to your identity provider without asking for an email in Forecastable. An existing provider session may sign you in immediately.
- Share the link in your company portal, onboarding instructions, or bookmarks.
/login page for password recovery. The ordinary email-first SSO flow also remains available.
Development and production have separate links and address settings. This feature needs no additional DNS records, certificates, or identity-provider callback URLs. An identity-provider application tile can open this link as its launch URL; it must start a Forecastable sign-in rather than send an unsolicited SAML assertion.
Sign-in policy
- Identity trust policy: Choose Company-managed identities (the default) or Verified email. See the full comparison.
- Require single sign-on: Off by default. When off, eligible existing accounts can use password, Google, or SSO. When on, ordinary members must use your provider; Google does not bypass this rule.
- SSO session length: Choose 1–24 hours. The default is 12 hours.
- Backup sign-in accounts: Choose up to five existing active users with native password sign-in in this organization. At least one is required before requiring SSO. SSO-only accounts cannot be backup accounts.
Test before requiring SSO
- Click Test sign-in and enter the work email of an existing account on a verified domain.
- Open the test in its new tab and finish your provider’s authentication flow.
- Confirm that the correct Forecastable account opens with its existing access.
- Test a backup account using password sign-in in a separate browser session.
- Enable Require single sign-on, save, and confirm the change.