Identity & lifecycle

Four moments in your app’s lifecycle interact with the SDK. Wire all four and the integration is complete. The code below is platform-agnostic; see the per-SDK lifecycle guides for exact syntax (Flutter, React Native, Swift).

1. App launch (every time)

The most common integration miss: users who installed your app before you added ClarioDesk never go through login again, so an “identify on login” hook alone leaves them as unlabeled devices. Hydrate from your own persisted session on launch and identify unconditionally. identify() is idempotent (same values = no-op write) and cheap (one signed POST, roughly 5 to 25 ms).

await ClarioDesk.init(apiKey: 'pk_live_…');
final user = await yourAuth.currentUser();
if (user != null) {
  await ClarioDesk.identify(externalId: user.id, email: user.email);
}

await ClarioDesk.init({ apiKey: 'pk_live_…' });
const user = await yourAuth.currentUser();
if (user) await ClarioDesk.identify({ externalId: user.id, email: user.email });

Right after your auth succeeds, call identify(). This overwrites the label on the existing device row, without registering a new device or generating a new key. The same device now carries the new user’s metadata.

3. Logout

With Verified identity, call clearIdentity() before signing the user out of your own app.

await ClarioDesk.clearIdentity();
await yourAuth.signOut();

await ClarioDesk.clearIdentity();
await yourAuth.signOut();

clearIdentity() preserves the device key, advances the signed identity epoch, and prevents old-account cache/network work from becoming visible to the next host user. In label-only mode, reset() remains the stronger shared-device isolation option.

4. User switch (A → B without restart)

Create and await the clearIdentity() intent, switch the host session, then verified-identify user B with a fresh proof.

Never activate user B before the clear intent exists, and never fall back to a label write after proof failure. reset() removes this installation; customer erasure is a separate owner/admin dashboard action.

What if I never call `identify()`?

Tickets still work. The device row exists and agents see a device id but no email, and the dashboard shows an “Unverified device” badge. Useful for anonymous-feedback flows; otherwise, wire case 1 above.

Introduction

Integration

Build with AI

Core concepts

Identity & lifecycle

1. App launch (every time)

3. Logout

4. User switch (A → B without restart)

What if I never call `identify()`?

​1. App launch (every time)

​2. Fresh login or signup

​3. Logout

​4. User switch (A → B without restart)

​What if I never call identify()?

1. App launch (every time)

2. Fresh login or signup

3. Logout

4. User switch (A → B without restart)

What if I never call `identify()`?