Help Center/Governance, RBAC & Security Desk/How to open "Devices" (Identity & Access) and read it
Governance, RBAC & Security Desk•Last updated: 2026-10-20•3 min read

How to open "Devices" (Identity & Access) and read it

Devices derived from sessions: one row per device fingerprint stored on i8_auth_sessions.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Open the screen

In the admin sidebar open the "Identity & Access" group and click "Devices" (address /admin/identity/devices). Under the title the line "Data: ..." names where the figures come from: Live: i8_auth_sessions (grouped by device fingerprint).

2

Read the KPI tiles

Tiles: "Distinct devices", "Devices with live sessions", "Devices shared by 2+ members". A tile that says "unavailable" means its source could not be read; it is never shown as zero.

3

Read the table

Columns: Device, Sessions, Members, Networks, Live now, Any MFA, First seen, Last session. Each row is one device fingerprint (masked) with how many sessions, members and networks it has had and how many sessions are live now. Sessions without a fingerprint are grouped as "(no fingerprint recorded)".

4

Revoke every live session on a device

Use "Revoke all live sessions on device" on the row. See "How to revoke all live sessions on a device". Super administrators only.

5

Know the limits

Devices are inferred from sessions; there is no separate device register, trust score or block list behind this screen. "Last session" is the start of the newest session, not last activity.

Expected Operational Outcome

You can read the live data and use the actions this screen really implements.

Troubleshooting & Failure Modes

Symptom: Failed to load identity/devices: HTTP 403
Likely Cause: The operations API requires an administrator principal.
Resolution: Sign in with an administrator account and click "Retry".
Symptom: A tile or the description says a table "has not been created in this database"
Likely Cause: A database section (918 or 919) has not been applied yet.
Resolution: Ask the platform owner to run npm run db:apply:insight-security. Until then the screen reports it and offers no write buttons.

Was this guide helpful?

Help us refine our platform documentation