Docs menu

Account

Single sign-on

Single sign-on comes with the paid plans, which are coming soon. This page describes it as it works.

Single sign-on lets your company's people sign in to KwikQA through the identity provider you already use, such as Okta, Entra ID, or Google Workspace. SSOJet connects that provider to KwikQA, and can also send KwikQA your directory's changes, which is directory sync. The Enterprise and BYOK Enterprise plans include single sign-on, directory sync, and the audit log.

Getting a connection

KwikQA sets up your company's connection with you. Write to support@kwikqa.com with the email domains your company signs in with, up to 20, and whether your directory should sync. KwikQA accepts a sign-in only from those domains, and each domain belongs to one company account. Your SSOJet tenant gets an External ID that names your company account; the Organization page shows it, with the connection's domains and status.

Signing in

  1. On the sign-in page, enter your work email under Company account and choose Continue with SSO.
  2. Your email's domain finds your company's connection, and SSOJet signs you in through your identity provider.
  3. KwikQA checks the sign-in and returns you to the dashboard, or to kwikqa.com/device when you were signing in the CLI.

Start and finish in the same browser, within 10 minutes. A sign-in must start at KwikQA: one that begins at your identity provider, such as an app tile in its dashboard, is refused as expired.

KwikQA accepts the sign-in only when your identity provider's token names your company's tenant, and your email is on one of its domains, exactly (a subdomain isn't accepted), and isn't marked unverified.

Who you sign in as

  • Someone already in the company account with that work email, invited before single sign-on, signs in as themselves, and their identity provider sign-in is linked to them.
  • A new address joins as a member, in no team, until a manager or admin adds them to one. With directory sync, the directory must have given the address access first.
  • An address that signed in before under another identity at your provider, as when someone's account there was deleted and made again, is refused until an admin suspends the old KwikQA account. The address may now belong to someone else, who mustn't see the old account. Then the new identity signs up as a new person.

Once single sign-on is on

  • Members sign in only through single sign-on. Asking for an emailed code sends none.
  • Invitations stop. People join by signing in, and managers add them to teams. Invitations sent before can't be used.
  • Admins sign in through single sign-on too, and can also ask for an emailed code if it fails, so a broken connection can't lock the company out. Each such sign-in is in the audit log, and the other admins get an email about it. Emergency codes are on until an admin turns them off on the Organization page.
  • Without directory sync, a member's sign-in through the identity provider counts for 30 days. After that, using the plan from the CLI or CI, including model requests and sharing insights, is refused until they sign in through it again:
    Acme signs in with single sign-on. Sign in with SSO at https://kwikqa.com/login/, then run the command again.
    Admins and CI tokens aren't held to the 30 days. npx kwikqa status still works.

Directory sync

SSOJet sends KwikQA each change to a person in your directory, and KwikQA applies each once, ignoring a change older than the last one it applied for that address. Directory groups aren't mapped to teams or roles.

  • Deactivated, deleted, or denied: the person is suspended. They're signed out everywhere, their own tokens stop working, and their account is erased after 30 days. CI tokens of the company or a team keep working. The company's last active admin isn't suspended; the audit log records why, and KwikQA's operators resolve it with you.
  • Created, updated, or activated again: a person the directory suspended is restored. Someone an admin suspended stays suspended.

Paused single sign-on

On a plan without single sign-on, such as Teams, or while KwikQA's operators pause the connection, people sign in with emailed codes again, and invitations work again. The connection, its domains, and people's linked identities are kept, so single sign-on works again with no new setup.

When a sign-in is refused

The sign-in page says why. A refusal after your identity provider returns you is also in the audit log.

ReasonWhat to do
Not set upNo company account has single sign-on for that address's domain, or it's paused. Use an emailed code, or ask your admins.
ExpiredStart again at the sign-in page, in one browser, within 10 minutes.
DeniedYour identity provider didn't sign you in, or your email isn't verified there. Ask your IT team.
Domain, or another company's accountSign in with your work email at the company whose account you're using.
Not provisionedYour directory hasn't given you access to KwikQA yet. Ask your IT team.
SuspendedYour company suspended your account. Ask one of its admins.
Signed in before as someone elseAsk an admin to suspend the old account, then sign in again.
FullThe company account has 500 people, its limit. Ask an admin to remove someone.
UnavailableSSOJet didn't answer. Try again in a moment.

The audit log

On the Enterprise plans, admins read the audit log on the Organization page. Besides people, teams, and tokens, it records single sign-on: each sign-in, linked identity, emergency code, and refusal with its reason; changes to the connection and to emergency codes; and each directory change, naming the person by work email, or only the domain for an address that isn't anyone's yet. It's kept for 400 days.