Kanshin Docs / Quickstart

Quickstart

Unlike the desktop products (Omnisnia CRM, Omni Core / Storyteller), which you install as a versioned build, Kanshin is a hosted service — there’s nothing to download. Your organization always runs on the current released version of the Kanshin console and identity service, delivered continuously: you’re on the latest release, and new capabilities arrive with no upgrade step on your side.

This page is the five-minute path. For the full guided tour, see Getting Started .

1. Open the console and sign in

Kanshin is in closed beta, and the hosted console is not open to the public yet. Ask us for access and we will send you your console address and a sign-in link. From there you land on the Welcome to Kanshin page — click Sign In. Kanshin hands you to its standards-based sign-in (OpenID Connect) and returns you to the console; it never asks for your password directly. New here? Create your account from the sign-in screen.

2. Create your organization

The first time in, Kanshin sends you to Create Your Organisation. Enter an Organisation Name and a short machine-friendly Slug (lowercase letters, numbers, hyphens), then click Create Organisation — you become its first administrator. Everything you manage (users, applications, groups, roles, policies) lives inside this organization and is fully isolated from every other tenant. See Organizations & Realms for the model.

3. Connect your first application

Open Applications → Clients in the left menu and register the app you want to protect with Kanshin sign-in — a web app, single-page app, native/mobile app, or a machine-to-machine service. You give it a name and its redirect URI(s), and Kanshin issues the client credentials you drop into your app’s OpenID Connect configuration, pointed at Kanshin’s issuer. See Applications for the full walkthrough and Application Access for controlling who may use it.

4. Bring in your team

  • Invite administrators to help run the tenant — see Members & Invitations .
  • Add the users of your applications by hand, or sync them from your existing directory automatically with SCIM provisioning .

Versioning — you’re always on the latest

The hosted console runs the current Kanshin release, delivered continuously: there’s no version to pick, download, or upgrade, and improvements land without any action on your side. That’s the key difference from the installable products, where you choose and run a specific versioned build. If you’re evaluating a self-managed or hybrid deployment — where you do run a pinned Kanshin release behind your own perimeter — start with Directory Integrations and reach out to us for the deployment guide.

Next steps