Start here
Introduction
Identise is an identity service: sign-up, sign-in, two-factor authentication, password reset and sessions for your apps, so your backend never stores a password.
There are two sides to Identise. The dashboard is where you manage your own account and your organisation's workspaces, applications, API keys and team. The API is what your apps call to sign their users in.
Add sign-in to your app
Create an application, generate an API key and sign your first user up in a few minutes.
Use the dashboard
Your account, two-factor authentication, sessions, workspaces and members.
How it fits together
Workspaces, applications, API keys, app users and the tokens your backend handles.
API reference
Every endpoint, what it takes and what it answers.
What you get
| Sign-up and sign-in | Email and password, and Sign in with Google. |
| Two-factor authentication | Authenticator apps (TOTP), with the secret stored encrypted. |
| Password reset and email verification | Emails in your own words and HTML; Identise fills in the code and link. |
| Sessions | Rotating refresh tokens, a device list per user, signing out one device or all of them. |
| Isolated users per app | The same email can be a separate account in two of your apps. |
| Platforms | A website builder or similar can create one isolated tenant app per customer through the API. |
| Audit logs | Who did what in a workspace, when, from which address and browser. |
Who these docs are for
Everyone with an Identise account: start with Your account and Workspaces and members. Developers connecting an app: follow the Quickstart, then the Integrate pages for each sign-in flow, and keep the Security checklist at hand before going live.