> ## Documentation Index
> Fetch the complete documentation index at: https://docs.forecastable.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Identity trust policies

> Understand company-managed identities, verified email, automatic account linking, and organization boundaries.

Choose the policy under **Settings > Single sign-on > Sign-in policy > Identity trust policy**. Both policies authenticate the person through your configured provider. The choice determines whether Forecastable relies on company control of work email addresses or requires an explicit email-ownership claim.

## Compare the policies

| Behavior | Company-managed identities | Verified email |
| - | - | - |
| Default | Yes, including existing configurations without a saved choice | No; select it explicitly |
| Requires `email_verified=true` | No; false or missing is allowed | Yes |
| Requires the configured provider | Yes | Yes |
| Requires an exact verified email domain | Yes | Yes |
| Automatically links an existing account in this organization | Yes | Yes |
| Links an account owned by another organization | Never | Never |
| Creates an unknown account | Never | May create a pending account in a non-invite-only organization |
| Assigns roles or permissions from provider claims | Never | Never |
| Allows a deleted account to sign in | Never | Never |

Selecting company-managed identities does not turn on **Require single sign-on**. Identity trust and mandatory SSO are separate settings.

## Company-managed identities

Use this policy when your organization controls account creation, work email assignment, and email changes in its identity provider. Users should not be able to register or edit their profile to claim a colleague's address. Restrict the Forecastable application to the intended directory users or groups.

Your provider's successful authentication and company-controlled email assignment are the trust source. Users do not need a separate email confirmation step just to satisfy Forecastable's `email_verified` check.

This policy is enabled by default for new organizations and for existing SSO organizations without an explicit saved trust policy. The default applies after the application update is deployed; no database backfill or provider claim change is needed. An explicitly saved Verified email choice is preserved through ordinary settings changes.

### What Forecastable checks

At the SSO callback, Forecastable:

1. Consumes the browser-bound server-side transaction created when sign-in started.
2. Exchanges the authorization code and retrieves the authoritative user attributes from Cognito.
3. For email-first sign-in, requires the returned email to match the email used to start sign-in. For a company sign-in link, obtains the email from the authenticated provider response; the server-side transaction already identifies the selected organization and provider.
4. Resolves that exact email domain through the organization's verified SSO domains.
5. Requires that organization and its active provider to match the sign-in transaction.
6. Requires a federated identity from that provider with a nonempty subject identifier.
7. Resolves an existing account or previously linked identity, then checks that it is active, belongs to this organization, and has the same email.
8. Links the provider identity without replacing the native password identity or granting a role.

An email domain match alone is insufficient. A provider configured by another organization cannot use this policy to claim your users. A verified parent domain does not authorize subdomains. A changed email on a previously linked identity must still match its Forecastable account; it cannot silently move that identity to another account.

### Prepare accounts

Create or invite each person into your Forecastable organization before their first company-managed SSO sign-in. Assign their normal membership and permissions. The work email must match the identity provider. Unknown users receive a sign-in error; this policy does not provision them automatically.

## Verified email

Use this policy when you need an explicit email-ownership assertion, or when users can register or edit their email without company approval. Your provider must send a trustworthy email verification claim, mapped to Cognito's `email_verified` attribute, with Boolean true or the string `true`.

False or missing claims reject sign-in, including repeat sign-ins from already linked identities. Merely storing an address or authenticating a user does not prove ownership of that address. Your provider can use an email confirmation step, a trusted upstream source, or an existing controlled verification process.

Do not hardcode every address as verified when users can choose unverified addresses. That would allow someone to claim another person's existing Forecastable account.

For an unknown user with a verified email, the existing pending-user behavior remains available in non-invite-only organizations. A pending user receives no effective role automatically. Invite-only organizations reject unknown users. Administrators must grant access explicitly.

## Authentik

Starting with Authentik 2025.10, its default email mapping returns `email_verified=false`. This can be expected behavior, rather than an invalid login.

* For a company-controlled directory, leave Forecastable on **Company-managed identities**. Keep the email mapping correct and ensure users cannot claim other people's addresses. You do not need to force email confirmation or change the false claim to true.
* For **Verified email**, follow Authentik's [email verification guide](https://docs.goauthentik.io/add-secure-apps/providers/oauth2/verify-email-address/). Replace the default email scope mapping with a custom mapping reflecting your real verification process. Clear or update verification whenever the address changes.

The same policy distinction applies to other compatible OIDC and SAML providers. There is no vendor-specific bypass.

## Switching policies

Save the policy and test a fresh SSO sign-in. A change invalidates previously issued SSO sessions; users authenticate again under the selected policy. Existing password identities, Google links, organization memberships, and roles remain intact.

Switching to Verified email can block users whose provider does not send a true verification claim. Test the provider and a native backup account before making the change. An invalid stored policy value falls back to verified-email enforcement; unsupported values submitted through settings are rejected.

This setting applies only to enterprise SSO. It does not relax Google sign-in's verified-email and authoritative-address requirements. It also does not grant additional access to other organizations where the person is a collaborator; normal membership permissions still apply.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.