Home / Product / Authentication

Bring people in

Give customers a complete path into—and back into—your product.

Handle account creation, sign-in, sessions, password recovery, and optional one-time codes.

See what it changes Technical guide ↗

Authentication in a product

A person arrivesCreate an account or sign in

Prove they own the accountPassword, recovery, or one-time code

Continue as the same personUse one identity across records and actions

Sign-in becomes product context

01Cover the account lifecycleSupport joining, returning, recovering access, and signing out.

02Give APIs a known callerCarry a session identity into product requests.

03Connect identity to real workThe signed-in account can own records and join teams.

Why it matters

Sign-in only matters when the rest of the product knows who arrived.

Create accounts, verify credentials, issue sessions, recover access, and connect each signed-in account to its records and groups. The application must create accounts, verify credentials, issue sessions, help people recover access, and connect the returning person to their data and teams.

Daptin includes account actions for sign-up, sign-in, password reset, and optional one-time-password verification. A successful session gives the resource and action paths the identity they need to make access decisions.

Each signed-in account carries its groups and record ownership into APIs, files, and actions.

Create accounts, verify credentials, issue sessions, recover access, and verify one-time codes in Daptin.

Start with the lifecycle every customer-facing product needs.

Keep sessions useful across the backend

Use the same caller identity in APIs, actions, files, and live experiences.

Add another factor when needed

Protect the whole account journey

Connect everyday sign-in, extra protection, and recovery.

The same account uses a protected password, a fresh one-time code, and an email recovery path through one consistent identity.

Diagram showing an account connected to password sign-in, one-time-code protection, email recovery, and a fresh sign-in after password reset. — **Protect sign-in and recovery**Recognize signed-in people and their teams, confirm authenticator setup, and require a fresh sign-in after a password change.Open diagram for full-size view

How it fits

Part of one connected backend.

Authentication does more when it can reuse the records, people, access rules, and workflows already in your application.

Step 1Enroll

Create the account and establish credentials.

Step 2Authenticate

Verify the chosen sign-in method.

Step 3Issue

Return a session token or browser session.

Step 4Use

The backend carries the account into access and ownership checks.

What it enables

Use it in products people recognize.

Start from the experience you want to create; the backend capability supports the work behind it.

Customer portal

People create accounts, recover access, and return to their own records.

Team product

Members sign in, join a workspace, and continue with team permissions.

Protected content

Subscribers authenticate before reaching private records and files.

Connected by design

Carry the signed-in account into ownership, groups, permissions, files, and actions.

These capabilities share the same application context, so each one makes authentication more useful.

Know the boundary

What Daptin leaves in your hands.

Configure TLS, signing and encryption secrets, sign-in throttling, recovery email, administrator access, and session lifetimes.

Understand the operating responsibility →

Build from one foundation

Accounts, sessions, recovery, and one-time codes use the same identity that owns records and joins groups.

Run Daptin locally, explore the live administration surface, and follow one complete application path.

Get Daptin Explore all capabilities