User log events

Review user sign-in activity

Depending on your Google Workspace edition, you might have access to the security investigation tool, which has more advanced features. For example, super admins can identify, triage, and take action on security and privacy issues. Learn more

As your organization's administrator, you can run searches and take action on User log events. For example, you can check critical actions carried out by users on their own accounts. These actions include changes to passwords, account recovery details (telephone numbers, email addresses), and 2-Step Verification enrollment. A login from an email client or a non-browser application is not logged in this report unless it’s a programmatic login from a session that was considered suspicious.

Note: If there’s no data for user log events during the previous 6 months, User log events might not be displayed in the left navigation menu.

Forward log event data to Google Cloud

You can opt in to share log event data with Google Cloud. If you turn on sharing, data is forwarded to Cloud Logging where you can query and view your logs and control how you route and store your logs.

The type of log event data you can share with Google Cloud depends on your Google Workspace, Cloud Identity, or Essentials account.

Run a search for log events

Your ability to run a search depends on your Google edition, your administrative privileges, and the data source. You can run a search on all users, regardless of their Google Workspace edition.

Audit and investigation tool

Security investigation tool

Supported editions for this feature: Frontline Standard; Enterprise Standard and Enterprise Plus; Education Standard and Education Plus; Enterprise Essentials Plus; Cloud Identity Premium. Compare your edition

To run a search in the security investigation tool, first choose a data source. Then, choose one or more conditions for your search. For each condition, choose an attribute, an operator, and a value.

Sign in with an administrator account to the Google Admin console.
If you aren’t using an administrator account, you can’t access the Admin console.
Go to Menu Security > Security center > Investigation tool.
Requires having the Security center administrator privilege.
Click Data source and select User log events.
Click Add Condition.
Tip: You can include one or more conditions in your search or customize your search with nested queries. For details, go to Customize your search with nested queries.
Click Attributeselect an option.
For a complete list of attributes, go to the Attribute descriptions section (later on this page).
Select an operator.
Enter a value or select a value from the list.
(Optional) To add more search conditions, repeat steps 4–7.
Click Search.
You can review the search results from the investigation tool in a table at the bottom of the page.
(Optional) To save your investigation, click Save enter a title and descriptionclick Save.

Notes

In the Condition builder tab, filters are represented as conditions with AND/OR operators. You can also use the Filter tab to include simple parameter and value pairs to filter the search results.
If you gave a user a new name, you will not see query results with the user's old name. For example, if you rename OldName@example.com to NewName@example.com, you will not see results for events related to OldName@example.com.

Attribute descriptions

For this data source, you can use the following attributes when searching log event data:

Attribute	Description
Actor group name	Group name of the actor. For more information, go to Filtering results by Google Group. To add a group to your filtering groups allowlist: Select Actor group name. Click Filtering groups. The Filtering groups page appears. Click Add Groups. Search for a group by entering the first few characters of its name or email address. When you see the group you want, select it. (Optional) To add another group, search for and select the group. When you finish selecting groups, click Add. (Optional) To remove a group, click Remove group . Click Save.
Actor organizational unit	Organizational unit of the actor
Affected user	Email address of the affected user
Challenge type*	The type of challenge used to verify the user, such as Password or Security Key Note: Newly added challenge types such as passkey may cause inconsistencies with existing challenge type called other for audit logs created before September 30, 2024.
Date	Date and time of the event (displayed in your browser's default time zone)
Domain*	The domain where the action occurred
Email forwarding address	Email address to forward the Gmail messages to
Event	The logged event action, such as 2-step verification enroll or Suspicious login Note: For the Logout event, even if the user signed in with login types other than Google Password, (such as Exchange, Reauth, SAML, or Unknown), the Login type for Logout events is displayed as Google Password.
IP address	IP address that the user used to sign in. Usually the address is the user's physical location, but it can be a proxy server or a Virtual Private Network (VPN) address.
Is second factor*	True if the user signed in with 2-factor authentication False if the user didn't sign in with 2-factor authentication
Is suspicious*	True if the sign-in attempt was suspicious and successful, otherwise false. Applicable only to the login_success event
Login time	If a Suspicious login event is blocked, this field displays the date and time the user tried to sign in.
Login type	Authentication method the user used: Exchange—When a user is authenticated by token exchange, such as via an OAuth login. It might also indicate the user was already signed in to a session when they signed in to another, and the 2 sessions were merged Google Password—Used a Google password. Includes sign-ins to less secure apps (if allowed) OIDC—Authentication by single sign-on OpenID Connect (OIDC). Reauth—User authenticated with a password re-authentication request SAML—Authentication by single sign-on Security Assertion Markup Language (SAML) Unknown**—User signed in using an unknown method
User	Email address of the user who performed the action

* You cannot create reporting rules with these filters. Learn more about reporting rules versus activity rules.

** Note for SAML users using the SSO profile for your organization (legacy SAML): If the SAML login attempt originates from an unknown device or IP address, or if there's a higher risk assessment, a failed login with the type Google Password is recorded in the log event. This occurs even if your SAML login is successful, because the system flags the initial attempt as suspicious. This failed login entry is then followed by a successful SAML login event. In legacy SAML, two login sessions are generated for a single SAML login. The first, often irrelevant session, is filtered out only if it's deemed non-suspicious.

Note: If you gave a user a new name, you will not see query results with the user's old name. For example, if you rename OldName@example.com to NewName@example.com, you will not see results for events related to OldName@example.com.