When an integration signs in to Enate with an Application Credential, it opens a User Session for the User that owns the credential. In the warehouse, that session looks the same as a person signing in as that User.

This makes it hard to report on who has really been using Enate. For example, a User that no person is allowed to sign in as can still show a sign-in every day, because an integration uses its Application Credential. Access reviews and audits can't tell integration activity from people.

Application Credentials are already in the warehouse, with their name and expiry date. What's missing is the link from each User Session to the Application Credential that opened it.

Idea: each User Session in the warehouse shows the Application Credential that opened it, or none if a person signed in. Reports could then:

separate integration sign-ins from people signing in

show the credential's name and expiry date next to each session

leave integration sessions out of active-user counts

Would this help you? Vote, and tell us in the comments how you'd use it, and whether you'd need it for past sessions as well as new ones.