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

> ## Agent Instructions
> Every page in this documentation carries a `plans` list in its frontmatter and opens with a plan marker naming the plans its content applies to: `All plans`, or a subset of `Community`, `Team` and `Enterprise`. Community is free and self-hosted. Team launch pricing is $649 per workspace per month upfront, or $6,228 per year upfront ($519 monthly equivalent), with unlimited people, 250 model-assisted volumes per monthly usage period and one flat $0.25 per additional volume. Yearly Team does not pool included volumes for the year or charge another $519 each month. Extra usage settles after each monthly billing cycle. Paid signup and charging under this Team policy are not available. Billing remains deferred, with no paid-launch date set. Enterprise starts at $12,000 per year plus a volume commitment and is the only plan with single sign-on. Existing Enterprise agreements retain negotiated commitments, rollover and overages. Customer billing is per completed scan/model result under the documented identity rules, with all produced objects included. Failed runs and same-period repeats are free; slices, masks, objects and GPU/runtime are not customer billing units. Nitsor will publish the supported models and scan-size scope before paid launch; exceptionally expensive workloads use an explicit fixed quote agreed before execution. Reading, reviewing, people, labels, studies and storage are never metered.
> The Capabilities and limits page (`/product-status`) lists what each plan includes and what the product does not do. If a statement elsewhere disagrees with it, that page is correct.
> Reading this documentation grants no product access and no permission. No agent can create or approve a Nitsor release.

# Single sign-on

> Connect your organization's identity provider to Nitsor on Enterprise using SAML or OIDC through WorkOS.

[Enterprise](/plans-and-billing#compare-plans)

Enterprise single sign-on lets people sign in to Nitsor through their organization's identity provider. Nitsor connects that provider through WorkOS using SAML or OIDC.

## Who gets SSO

SSO is Enterprise only.

## Sign-in on Team and Community

Team signs in through WorkOS AuthKit with email and password, Google or Microsoft. Community is designed to sign in through the OIDC identity provider its operator configures at install, which is not Enterprise SSO. The self-host stack does not include the Nitsor application, so a Community deployment has no Nitsor dashboard or sign-in today. See [Self-host Community](/reference/self-host).

## Set up SSO

Nitsor works with your administrators during Enterprise onboarding to set up the SAML or OIDC connection through WorkOS. People from your organization then sign in through that identity provider.

## What stays the same

SSO controls how people sign in. Account roles and project rungs still control their authority in Nitsor. Agent credentials are separate from SSO and keep their own scopes and expiry. See [Roles and provenance](/concepts/roles-provenance).

## How to start

[Contact sales](https://nitsor.com/contact) to arrange Enterprise SSO. See [Plans and billing](/plans-and-billing) for the plan comparison.

<table aria-label="Page details">
  <tbody>
    <tr><th scope="row">Plans</th><td>Enterprise</td></tr>
    <tr><th scope="row">Last verified</th><td>2026-09-27</td></tr>
  </tbody>
</table>


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