Skip to main content
The SIS Dashboard is the web console at 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:
  • — portable, KYC-verified identity, the “Proof of Personhood” a user carries across products.
  • — an agent’s scope-bound tasking run: Intent → Authorization → Vigilance.
  • — the money agent acting on a user’s behalf.
  • — 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.

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

TaskWhere
Create and configure your organisationOrganisation → Settings
Create environments (dev, staging, prod)Environments page
Connect Dynamic or Privy as your auth providerEnvironment → Authentication tab
Manage CORS origins for browser requestsEnvironment → CORS tab
Create API keys for server-to-server callsAPI Keys page
Invite and manage team membersOrganisation → Members

How It Fits

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.
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 — organisation, environment, auth provider, API key, and a live verifier call in one pass. For deeper background, the core concepts page covers how organisations and environments relate, and auth provider setup and API keys are the two configuration surfaces you’ll return to most. Start by minting a key. Everything else hangs off it.