Workspace Studio log events

View user and agent activity in Google Workspace Studio

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 security issues related to Google Workspace Studio log events. For example, you can view a record of actions to track user activity in Studio. You can also track how users create, edit, share, and run skills, and which steps flows complete on behalf of their owners. This information helps you troubleshoot issues or investigate unexpected changes.

Flows take actions on behalf of their owners. For actions in Google services, these events are logged in the corresponding service, with the owner as the actor. If you see abnormal activity by a user in a service that you think is because of a flow, you can stop the flow. Learn more about stopping users' flows

Skill log events only track activity for Gemini in Workspace skills managed in Studio. They don't track skills in the Gemini app or Gemini Enterprise. You can also manage how people in your organization create and use skills or share skills externally.

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

To run a search for log events, first choose a data source. Then, choose one or more filters for your search.

  1. In the Google Admin console, go to Menu and then Reporting and then Audit and investigation and then Workspace Studio log events.

    Requires having the Audit and investigation tool administrator privilege.

  2. To filter events that occurred before or after a specific date, for Date, select Before or After. By default, events from the last 7 days are shown. You can select a different date range or click to remove the date filter.

  3. Click Add a filter and then select an attribute. For example, to filter by a specific event type, select Event.
  4. Select an operator and then select a value and then click Apply.
    • (Optional) To create multiple filters for your search, repeat this step.
    • (Optional) To add a search operator, above Add a filter, select AND or OR.
  5. Click Search. Note: Using the Filter tab, you can include simple parameter and value pairs to filter the search results. You can also use the Condition builder tab, where the filters are represented as conditions with AND or OR operators.

Security investigation tool

Supported editions for this feature: Frontline Standard and Frontline Plus; 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.

  1. In the Google Admin console, go to Menu and then Security and then Security center and then Investigation tool.

    Requires having the Security center administrator privilege.

  2. Click Data source and select Workspace Studio log events.

  3. To filter events that occurred before or after a specific date, for Date, select Before or After. By default, events from the last 7 days are shown. You can select a different date range or click to remove the date filter.

  4. 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.
  5. Click Attribute and then select an option. For example, to filter by a specific event type, select Event.
    For a complete list of attributes, go to the Attribute descriptions section later on this page.
  6. Select an operator.
  7. Enter a value or select a value from the list.
  8. (Optional) To add more search conditions, repeat the steps.
  9. Click Search.
    You can review the search results from the investigation tool in a table at the bottom of the page.
  10. (Optional) To save your investigation, click Save and then enter a title and description and then click 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 give 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.
  • You can only search for data in messages that have not yet been deleted from Trash.

Attribute descriptions

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

Attribute Description

Actor

Email address of the user who performed the action, or whose flow performed the action on their behalf.
Agent info To search by AI agent info, select Agent info, and then select a nested column: Agent ID, Agent name, or Agent product. Search results are shown in the Agent ID column.

Click an entry in the search results to open the Log details panel to show:

  • Agent ID—The agent's unique ID.
  • Agent name—The agent's display name.
  • Agent product—The service the agent used (only supported by Google Workspace Studio flow).

Note: Additional agents will be supported later.
By an agent Action was performed with an AI agent (True or False)

Event

The logged event action. These include:

Flow events

  • Create flow: The user created a flow.
  • View flow: The user viewed a flow.
  • Edit flow: The user edited a flow.
  • Delete flow: The user deleted a flow.
  • Turn on: The user turned on a new flow for the first time or saved changes to a flow that was already on.
  • Turn on again: The user turned on a flow that had been turned off.
  • Turn off: The user turned off a flow.
  • Start run: The flow started a run.
  • End run success: The run finished successfully.
  • End run with error: The run stopped due to an issue.
  • Stop run: The run stopped for another reason.
  • Start step: The run started a step.
  • End step: The run completed a step.
  • Block step: A Workspace admin policy blocked a step action.
  • Pause run: The run was paused.
  • Resume run: The flow resumed a run.

Skill events

  • Skill was created: The user created a skill.
  • Copy skill: The user made a copy of a skill.
  • Update skill: The user updated a skill's name or details.
  • Update skill content: The user edited a skill's instructions or resources.
  • Link skill resource: The user linked or unlinked a resource in a skill.
  • Sync skill from source: A skill synced updates from its linked Google Docs document.
  • Commit skill content: The user saved a new version of a skill's content.
  • Change skill sharing level: The user changed who can access a skill.
  • Accept shared skill: The user accepted a skill shared with them.
  • Execute skill: The user ran a skill.
  • Enable skill: A skill was turned on.
  • Disable skill: A skill was turned off.
  • Delete skill: The user deleted a skill.

Flow ID

The ID of the flow.

Flow name

The name of the flow.

Run ID

The ID of an individual run by a flow.

Step type

The type of step, which can be one of the following:

  • Trigger: The step was a starter, the first step of the flow.
  • Action: The step was after the starter and wasn't a condition step.
  • Condition evaluation: The step was a Check if step.

Step name

The name of the step that was run by the flow.

Step app

 The app the step uses for the task, such as Gmail, Chat, or a linked third-party service.

Run length

 How long it took to complete the run, in seconds.

Run type

How the run was started, which can be:

  • test run: The run was started by the user using a test run.
  • execution: The run was started automatically by the flow starter detecting a starting event.

Turn off reason

Why a flow was turned off:

  • Turned off by user: The user turned it off.
  • Turned off by step: A step stopped working and turned off the flow.
  • Account deleted: The user no longer has a Workspace account.
  • Run error: Too many runs in a row didn't complete successfully.
  • No access to Studio: The user lost access to Workspace Studio.
  • Turned off by Google: A Google Workspace Support agent turned off the flow.

Skill ID

The ID of the skill.

Skill name

The name of the skill.

Skill creation method

How the skill was created:

  • Created manually: The user wrote the skill instructions directly.
  • Created using NL: The user generated the skill from a natural language (NL) prompt in Studio.
  • Created in Docs: The user created the skill from a Google Docs document.

Skill template ID

The ID of the template used to create the skill.

Source doc ID

The ID of the Google Docs document linked as the source for the skill.

Source doc revision ID

The version ID of the linked Google Docs document when the skill was synced.

Source skill ID

The ID of the original skill when the user copies a skill.

Skill revision ID

The version ID of the skill.

Has instruction change

Shows whether an update changed the skill's instructions. Values are true or false.

Referenced resource count

The number of resources linked to the skill.

Resource action

Whether a resource was added to or removed from the skill:

  • Resource linked: A resource was linked to the skill.
  • Resource unlinked: A resource was unlinked from the skill.

Sync status

The result of syncing a skill with its source Google Docs document:

  • Success: The skill synced with the latest document changes.
  • Failure: The skill couldn't sync with the source document.
  • New update available: The source document has new changes ready to sync.

Skill sharing level

Who the skill is shared with:

  • Private: Only specific people or the owner can access the skill.
  • Domain-wide: People in your organization can access the skill.
  • Public: Anyone outside your organization with the link can access the skill.

Skill execution location

Where the user ran the skill:

  • Studio chat: In Google Workspace Studio.
  • Docs sidebar: In the Gemini side panel in Google Docs.
  • Sheets sidebar: In the Gemini side panel in Google Sheets.
  • Slides sidebar: In the Gemini side panel in Google Slides.
  • Chat annotation: In Google Chat.

Skill disablement reason

Why a skill was turned off:

  • Disabled by user: The user turned off the skill.
  • Disabled by admin: An administrator turned off the skill.
  • Disabled by Google: Google turned off the skill.

Delete time

The date and time when the skill was deleted. You can't create reporting rules with this filter. For details, go to Admin access to reporting rules & activity rules.

Manage log event data

Manage search results column data

You can control which data columns appear in your search results.

  1. At the top-right of the search results table, click Manage columns .
  2. (Optional) To remove current columns, click Remove .
  3. (Optional) To add columns, next to Add new column, click the Down arrow and select the data column.
    Repeat as needed.
  4. (Optional) To change the order of the columns, drag the data column names.
  5. Click Save.

Export search result data

You can export search results to Sheets or to a CSV file.

  1. At the top of the search results table, click Export all.
  2. Enter a name and then click Export.
    The export displays below the search results table under Export action results.
  3. To view the data, click the name of your export.
    The export opens in Sheets.

Export limits vary:

  • The total results of the export are limited to 100,000 rows.
  • If you have the security investigation tool, the total results of the export are limited to 30 million rows.

For more information, go to Export search results.

When and how long is data available?

Take action based on search results

Create activity rules & set up alerts

  • You can set up alerts based on log event data using reporting rules. For instructions, go to Create and manage reporting rules.
  • Supported editions for this feature: Frontline Standard and Frontline Plus; Enterprise Standard and Enterprise Plus; Education Standard and Education Plus; Enterprise Essentials Plus; Cloud Identity Premium. Compare your edition

    To help prevent, detect, and remediate security issues efficiently, you can automate actions in the security investigation tool and set up alerts by creating activity rules. To set up a rule, set up conditions for the rule, and then specify the actions to perform when the conditions are met. For more details, go to Create and manage activity rules.

Take action based on search results

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

After you run a search in the security investigation tool, you can act on your search results. For example, you can run a search based on Gmail log events, and then use the tool to delete specific messages, send messages to quarantine, or send messages to users' inboxes. For more details, go to Take action based on search results.

Manage your investigations

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

View your list of investigations

To view a list of the investigations that you own and that were shared with you, click View investigations . The investigation list includes the names, descriptions, and owners of the investigations, and the date last modified.

From this list, you can take action on any investigations that you own, for example, to delete an investigation. Check the box for an investigation and then click Actions.

Note: You can view your saved investigations under Quick access, directly above your list of investigations.

Configure settings for your investigations

As a super administrator, click Settings to:

  • Change the time zone for your investigations. The time zone applies to search conditions and results.
  • Turn on or off Require reviewer. For more details, go to Require reviewers for bulk actions.
  • Turn on or off View content. This setting allows admins with the appropriate privileges to view content.
  • Turn on or off Enable action justification.

For more details, go to Configure settings for your investigations.

Save, share, delete & duplicate investigations

To save your search criteria or share it with others, you can create and save an investigation, and then share, duplicate, or delete it.

For details, go to Save, share, delete, and duplicate investigations.