Location and provider context on user profiles

A user row that only shows email is hard to investigate. Support needs the connected authentication provider and recent location context next to the profile, and the dashboard needs the same dimensions when comparing events.

User and dashboard views now surface that context, backed by a current-user API for profile data.

This is the longer note behind the April 12 changelog entry.

How it works

The user detail page shows the connected provider next to the profile (icon and label, including social connectors such as Google). The users table can filter by provider.

Location and provider also appear as comparison dimensions on the dashboard and audit overview, so you can line up activity by where it came from and which IdP completed the sign-in.

The current-user API returns profile data for the authenticated subject in the environment, including group memberships (currentUserGroups). Console views use that profile payload rather than a separate ad-hoc lookup.

Location on a profile or event is the location Authdog recorded for that session or event. It is not a proof of physical presence.

Set it up

In the console, open Users:

1. Open a user and confirm the connected provider is visible.
2. Return to the dashboard or Audit and compare events by location and provider.

No extra add-on is required. Provider labels follow the connection that created or linked the user.

Trust boundaries

Provider and location summaries are observational. They do not change authorization. A missing location is not proof the action never happened; older events may lack the field.

Do not treat a provider badge as MFA. It only names the connection used.

Try it

Open a user who signed in with a social connection, then filter audit by that provider. User model notes are in Users. The original release note is in the changelog.