Configure organization sign-in
Edition: Enterprise Compare editions
Connect Google Workspace, Okta, or custom OAuth2, verify your domain, and manage member permissions.
Connect Google Workspace, Okta, or a custom OAuth2 provider so verified work accounts can join your organization. You need organization administrator access and permission to add DNS records for your team's email domain.
1. Connect your identity provider
Open Organization → Authentication, choose a provider, and enter your work
email domain, such as example.com.
Google Workspace: Glossia manages the Google connection. You do not need to create an OAuth or SAML application or register a callback address.
Okta: Create an OpenID Connect web application.
Register the redirect address displayed in Glossia, then enter the application's
client ID, client secret, and HTTPS issuer. Glossia supports standard Okta
organization issuers and the /oauth2/default authorization server. Secrets are
encrypted at rest; leaving the secret blank when editing preserves its saved value.
Custom OAuth2: Register an authorization-code application at your provider with the redirect address displayed in Glossia. Choose Custom OAuth2 and enter its base URL, authorization URL, token URL, user-information URL, client ID, and client secret. All endpoints must use HTTPS on port 443 without URL credentials, query strings, or fragments. Token and user-information endpoints must resolve only to public internet addresses. Private-network identity providers are not supported, and Glossia does not follow endpoint redirects.
The provider must support PKCE (S256), HTTP Basic client authentication at the
token endpoint, and the openid email profile scopes. Its user-information
response must include a stable string sub, an email in the verified work
domain, and boolean email_verified: true. Glossia does not infer verified
ownership from an email string alone.
Select Save authentication settings.
2. Verify your domain
At your DNS provider, add the record shown in Verify domain ownership:
| Field | Value |
|---|---|
| Type | TXT |
| Name / Host | The Record name displayed in Glossia, such as _glossia-verification.example.com |
| Value / Content | The Record value displayed in Glossia, starting with glossia-domain-verification= |
If your DNS provider appends the domain automatically, enter only
_glossia-verification as the host. Return to Glossia and select Verify domain.
If verification fails, check both values and allow time for DNS propagation.
Keep the record in place after verification.
3. Test organization sign-in
Ask a team member to enter their work email on the login page and select Continue with your organization. Google Workspace members can also use Log in with Google.
A verified identity with an exact matching email domain automatically joins with basic read access. Google also requires a valid hosted-domain claim; a personal Google account with the same email suffix does not qualify. Use member permissions to grant more access.
To link a new work identity to an existing Glossia account, first sign in
with that account's established method, then visit /auth/login and start
organization sign-in. Matching an email address alone never links accounts.
Keep access working
- Glossia rechecks DNS daily. Verification expires 30 days after the last successful check; if the record disappears, restore it and verify again before that deadline to avoid interrupting sign-in.
- Changing the domain or provider clears verification. Verify again before members can use organization sign-in. Changing or disabling the provider also removes credentials belonging to the previous provider.
- Disabling sign-in does not delete memberships. Removing a member blocks automatic re-enrollment until an administrator explicitly adds or invites them again.
Authentication settings, invitations, access credentials, model editing, and organization deletion remain administrator responsibilities. Administrators can review configuration changes, domain verification, permission changes, and successful sign-ins in Organization → Audit logs. See Audit logs.
SSO uses OpenID Connect or custom OAuth2, not SAML. Use SCIM provisioning to manage membership from your identity provider. Users newly created by SCIM can link their first verified organization identity without a prior login; existing users still follow the account-linking process above.
Require organization sign-in
After verifying your domain, sign in with your administrator account through the organization provider, then open Authentication → Require single sign-on and select Enforce SSO. Glossia requires this tested session to avoid locking you out with an untested provider.
Enforcement applies to signed-in browser access to this organization, including existing sessions and subsequent LiveView interactions. A Google or Okta session for a different organization does not qualify. Personal accounts and other organizations remain accessible through their existing login methods.
Enforcement does not change API, CLI, or MCP token authentication, and it does not hide anonymously accessible public content. Deprovisioning and credential revocation are separate controls.
Disable enforcement before changing or removing provider settings. Keep domain
verification current: expired ownership blocks enforced browser access until
ownership is verified again. Self-hosted operators can renew verification using
the domain verification worker or disable enforcement through the application
console if no administrator can sign in. Administrators can also disable it
using REST or MCP with an existing organization:admin credential. See the
organization authentication API reference.
If Google blocks sign-in
If your organization restricts third-party apps, a Google Workspace administrator may need to approve Glossia:
- In the Google Admin console, open Security → Access and data control → API controls → Manage third-party app access.
- Find Glossia among accessed apps, or use Configure new app to search by name or OAuth client ID. This is Glossia's shared connection, not an app you need to create.
- Review its permissions, allow the relevant users according to your policy, and retry sign-in after the change takes effect.
See Google's third-party app access guide for access levels and administrator requirements.