Login As Event Type

Login As events contain details about what a Salesforce admin did while logged in as another user.

Login As Event Type is used by EventLogFile (ELF). It isn’t a real-time event. For the LoginAsEvent real-time event, which is part of Real-Time Event Monitoring (RTEM), see LoginAsEvent in the Platform Events Developer Guide.

For details about event monitoring, see the Trailhead Event Monitoring module or REST API Developer’s Guide.

Bolster your security posture by receiving alerts and blocking potentially malicious LoginAsEvent activities with a Transaction Security policy.
  • Type: String
  • Description: The IP address of the client that’s using Salesforce services. A Salesforce internal IP (such as a login from AppExchange) is shown as “Salesforce.com IP”.
  • Example: 96.43.144.26
  • Type: Number
  • Description: The CPU time in milliseconds used to complete the request. This field indicates the amount of activity taking place in the app server layer.
  • Type: Id
  • Description: The 15-character ID of the user who’s using Salesforce services through the UI or API. In this case, the user who’s doing the impersonation.
  • Type: Id
  • Description: The 18-character case-insensitive ID of the user who’s using Salesforce services through the UI or API. In this case, the user who’s doing the impersonation.
  • Type: String
  • Description: The username of the user who’s using Salesforce services through the UI or API. In this case, the user who’s doing the impersonation.
  • Type: String
  • Description: The type of event. The value is always LoginAs.
  • Type: String
  • Description: The string that ties together all events in a given user’s login session. It starts with a login event and ends with either a logout event or the user session expiring.
  • Example: GeJCsym5eyvtEK2I
  • Type: Id
  • Description: The 15-character ID of the organization.
  • Example: 00D000000000123
  • Type: String
  • Description: The unique ID of a single transaction. A transaction can contain one or more events. Each event in a given transaction has the same REQUEST_ID.
  • Example: 3nWgxWbDKWWDIk0FKfF5DV
  • Type: Number
  • Description: The amount of time that the request took in milliseconds.
  • Type: String
  • Description: The user’s unique session ID. You can use this value to identify all user events within a session. When a user logs out and logs in again, a new session is started.
  • Example: d7DEq/ANa7nNZZVD
  • Type: String
  • Description: The access time of Salesforce services in GMT.
  • Example: 20130715233322.670
  • Type: DateTime
  • Description: The access time of Salesforce services in ISO8601-compatible format (YYYY-MM-DDTHH:MM:SS.sssZ). The timezone is GMT.
  • Example: 2015-07-27T11:32:59.555Z
  • Type: String
  • Description: The URI of the page that’s receiving the request.
  • Example: /home/home.jsp
  • Type: ID
  • Description: The 18-character case-insensitive ID of the URI of the page that’s receiving the request.
  • Type: Id
  • Description: The 15-character ID of the user who’s using Salesforce services through the UI or the API.
  • Example: 00530000009M943
  • Type: Id
  • Description: The 18-character case-insensitive ID of the user who’s using Salesforce services through the UI or the API.
  • Example: 00590000000I1SNIA0