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

# SIS Dashboard

> The SIS Dashboard is the developer console for configuring your Sumvin Identity Service integration.

The SIS Dashboard is the web console at [dash.sis.sumvin.com](https://dash.sis.sumvin.com) for developers building on Sumvin's federated identity platform. **Configure here, integrate once — the dashboard is where the envelope is drawn, not where the traffic runs.**

## What You Build With It

The dashboard is the front door to the products you ship on Sumvin:

* <Tooltip headline="Sigil" tip="Sumvin's portable, KYC-verified identity — Proof of Personhood a user carries across products." cta="Learn more →" href="/identity/overview">Sigil</Tooltip> — portable, KYC-verified identity, the "Proof of Personhood" a user carries across products.
* <Tooltip headline="Errand" tip="An agent's scope-bound tasking run — Intent, Authorization, Vigilance." cta="Learn more →" href="/concepts/errands">Errand</Tooltip> — an agent's scope-bound tasking run: Intent → Authorization → Vigilance.
* <Tooltip headline="Envoy" tip="The money agent acting on a user's behalf." cta="Learn more →" href="/overview/personas/agent-flows">Envoy</Tooltip> — the money agent acting on a user's behalf.
* <Tooltip headline="Atomic Money" tip="Payments, ramps, cards, and settlement." cta="Learn more →" href="/products/atomic-money/overview">Atomic Money</Tooltip> — payments, ramps, cards, and settlement.

Configuring SIS here is how your users' identities — their Sigils — get resolved when these products run. You draw the envelope in the dashboard; the products run against it.

<Snippet file="product-term-disambiguation.mdx" />

## Who It's For

Engineering teams integrating auth flows on top of Sumvin's federated identity — whether you're connecting a wallet, agent, or financial identity and want to configure how SIS validates your users.

## What You Can Do

| Task                                           | Where                            |
| ---------------------------------------------- | -------------------------------- |
| Create and configure your organisation         | Organisation → Settings          |
| Create environments (dev, staging, prod)       | Environments page                |
| Connect Dynamic or Privy as your auth provider | Environment → Authentication tab |
| Manage CORS origins for browser requests       | Environment → CORS tab           |
| Create API keys for server-to-server calls     | API Keys page                    |
| Invite and manage team members                 | Organisation → Members           |

## How It Fits

<Note>
  Your app authenticates users via Dynamic or Privy → your app passes their JWT to SIS → SIS validates against your configured provider for that environment and resolves the user's Sumvin identity.
</Note>

Setting up this pipeline is what the dashboard is for. Each environment is fully isolated — its own provider configuration and its own SIS API credentials — so you can run development, staging, and production side by side without one bleeding into another.

## Get Started

The fastest way in is the [quickstart](/dashboard/quickstart) — organisation, environment, auth provider, API key, and a live verifier call in one pass. For deeper background, the [core concepts](/dashboard/organisations) page covers how organisations and environments relate, and [auth provider setup](/dashboard/auth-providers) and [API keys](/dashboard/api-keys) are the two configuration surfaces you'll return to most. **Start by minting a key. Everything else hangs off it.**