Topic starter
06/06/2026 11:28 am
TL;DR: Active users, new versus returning users, and organization-level engagement are now surfaced directly inside AuthKit by AuthKit Analytics, replacing custom event wiring and third-party dashboards for teams that need a quick read on growth patterns, according to WorkOS. The real governance value is clearer visibility into authentication behaviour, but it does not remove the need for a separate identity analytics and control model.
Editorial analysis by NHI Mgmt Group, based on content published by WorkOS: “AuthKit Analytics: Understand user growth at a glance”.
Key questions
Q: How should teams use authentication analytics without confusing it with governance?
A: Treat authentication analytics as an input to governance, not as governance itself.
Q: What are the best ways to interpret new versus returning users in an IAM context?
A: Treat new versus returning users as a sign of adoption pattern, not as proof of security posture.
Q: What breaks when authentication data is kept only in external dashboards?
A: When authentication metrics live only in external dashboards, teams often lose the speed and consistency needed to spot usage changes early.
Practitioner guidance
- Define the identity questions your auth layer should answer Map which metrics belong in authentication analytics, such as active users and returning sessions, versus which still require lifecycle, entitlement, or compliance reporting.
- Review tenant-level adoption patterns regularly Use organisation-level views to spot customer accounts that are growing, stagnating, or generating sign-ups without sustained usage.
- Cross-check analytics against your existing source of truth Compare built-in authentication metrics with the reports already maintained in your broader IAM or product analytics stack so drift is visible.
Bottom line: Authentication analytics improves visibility into growth patterns, but it remains an observability layer rather than a governance control.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 3 days ago by NHI Mgmt Group
06/06/2026 12:18 pm
Authentication visibility is not the same as identity governance. Surfacing active users, returning users, and organisational growth inside the authentication layer improves operational awareness, but it does not answer who should have access, who owns the account, or whether privileges remain appropriate. The governance value is real, but it is narrower than many teams assume. Practitioners should treat this as an observability gain, not a control model.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What should IAM teams do when login trends and access decisions point in different directions?
A: Treat the mismatch as a governance signal, not as a data error. If login activity suggests growth while access reviews or offboarding records show stale accounts, the programme has a control boundary problem. The right response is to separate usage analytics from entitlement management and resolve the process that owns each decision.
👉 Read our full editorial: Authkit analytics puts authentication growth data into view
This post was modified 3 days ago by NHI Mgmt Group