Security
Single sign-on, two-factor authentication, passkeys, sessions, API keys and AI app access.
This page covers how your workspace keeps sign-in and access safe: single sign-on for the whole workspace, the protections each person turns on for their own account, and the keys and connections that let other systems reach your data.
Single sign-on
Single sign-on (SSO) lets your team sign in through your organization's identity provider instead of a XODASH password. XODASH supports Okta, Azure AD (Microsoft Entra ID), Google Workspace, Auth0, OneLogin, and any provider through Custom SAML or Custom OIDC.
Who can do this
Only workspace Admins see Settings > SSO. SSO signs in people who already have an account, so invite your team with the same email addresses your identity provider uses.
Set up SSO
Copy your workspace's SSO URLs
Go to Settings > SSO. Under Your SSO URLs, copy the ACS URL (SAML), Audience URI / Entity ID (SAML) or Callback URL (OIDC) your provider needs. They're unique to your workspace. Setup Guides on the same tab walk through each provider.
Create the app in your identity provider
Add XODASH as an app in your provider and paste in the URLs from the previous step. Send the user's email and name as attributes.
Configure SSO in XODASH
Select Configure SSO, choose your Identity Provider and give it a Configuration Name.
For SAML, paste the IdP Metadata URL, or enter the IdP Entity ID, SSO URL (Login URL)
and X.509 Certificate. For OIDC, enter the Discovery URL, Client ID and
Client Secret. Set the Email Attribute and Name Attribute, usually email and name.
Test it
New configurations start Disabled. Select Test to check XODASH can reach your provider.
Turn it on
Under Enable SSO, select Disabled to switch it to Enabled. People can now use Continue with SSO on the sign-in page.
To change the setup later, select Edit. Service Provider Metadata shows the values to give your identity provider administrator.
Enforce SSO
Once SSO is enabled, you can require it. Under Enforce SSO, select Optional to switch it to Enforced.
Check SSO works before you enforce it
When SSO is enforced, nobody can sign in with a password, admins included. Sign in through SSO yourself first. If you turn SSO off, enforcement stops too.
Enforcing SSO turns off password sign-in only. People who've added a passkey can still sign in with it.
Remove SSO
Under Delete Configuration, select Delete and confirm. Everyone goes back to password sign-in. This can't be undone; to use SSO again, configure it from the start.
Two-factor authentication
Each person turns on two-factor authentication for their own account. Once it's on, XODASH asks for a 6-digit code from an authenticator app after their password. There's no workspace setting that requires it, so ask your team to set it up.
Start setup
Go to Settings > Profile and, under Authenticator App (TOTP), select Set up authenticator.
Scan the QR code
Scan the code with your authenticator app, then select I've scanned the QR code. If you can't scan it, open Can't scan? Enter the setup key manually.
Save your backup codes
Copy your 8 backup codes somewhere safe, then select I've saved my backup codes. They're shown only once, and each one works once.
Confirm
Enter the 6-digit code from your app under Verification code and select Enable 2FA.
When it's on, you can select Regenerate backup codes (enter a current code; your old backup codes stop working) or Disable 2FA (enter your current password).
After 5 wrong codes at sign-in, code checks lock for 15 minutes. If you've lost your phone, sign in with a backup code.
Passkeys
A passkey signs you in with Touch ID, Face ID, Windows Hello or a hardware security key, with no password. Passkeys resist phishing and are tied to your device or password manager.
Name it
In Settings > Profile > Passkeys, type an optional Passkey name, such as "Work laptop".
Add it
Select Add Passkey and follow your browser's prompt.
Each passkey shows when it was added and last used, and Synced if your password manager backs it up. Select its name to rename it, or the trash icon to remove it straight away. If your browser doesn't support passkeys, you'll see a note suggesting a modern browser.
Sessions
Each person chooses how long they stay signed in under Session Duration in Settings > Profile. Pick 4 hours, 8 hours (recommended), 24 hours, 7 days or 30 days. Changes apply the next time you sign in.
Whatever you choose, XODASH signs you out after 24 hours without activity. Choosing 30 days asks you to confirm, because anyone with your device could use your account for up to a month.
Sign-in limits
XODASH slows down repeated guessing on its own. Too many wrong passwords or two-factor codes pause sign-in for that account for a while, and requests for password resets and workspace links are limited per email address. People see how long to wait. See Too many attempts.
API keys
API keys let your website and other systems send leads to XODASH or read and write your data through the API.
Who can do this
Only workspace Admins see Settings > API.
Start a new key
Go to Settings > API and select Create API Key.
Name it and choose scopes
Give it a Key Name, such as "Website Lead Form". Under Scopes, choose what the key can do, such as Web Lead Ingestion or Read People. New keys start with no permissions, so pick at least one. For lead keys, you can add Lead Notification Emails to be told about each new lead.
Create and copy it
Select Create Key. Copy the key with Copy Key, store it somewhere safe, and then confirm you've saved it to close the dialog. This is the only time you'll see the whole key.
Keys are for server-side use only. Never put an API key in website or mobile app code that people can see.
The list shows each key's name, scopes, the start of the key, when it was created and when it was last used.
Delete a key
Select Delete on the key, then Delete Key. Anything using it stops working straight away, and the key can't be recovered. If you lose a key, delete it and create a new one. For the API itself, see REST API.
AI app connections
People can connect AI apps to XODASH from Settings > AI Apps. The apps work with XODASH data using that person's role. Admins can turn off Allow AI app connections to block every connected AI app in the workspace at once, and can see everyone's connected apps with Show everyone. Anyone can Disconnect their own. See MCP server.