---
title: "Correlating Workday Audit Events with AI Assistant Tool…"
description: "Which Workday reports show an assistant’s action, which calls leave no web-service log, and what a zero-payload connector can add."
url: https://kiweely.com/guides/correlating-workday-audit-with-ai-assistant-calls
---

# Correlating Workday Audit Events with AI Assistant Tool Calls

Workday’s agent audit separates the agent account from the person it acted for. Ordinary web-service reads are a weaker trail: Workday does not log GET or unsuccessful web-service requests. A user-delegated connector still acts as the worker, and its own telemetry omits names and pay.

-   **Checked** against Workday on November 16
-   Applies to **Workday Extend**
-   5 min read
-   Published November 16
-   By Kiweely

Correlating Workday Audit Events with AI Assistant Tool Calls

Join the trails on purpose. Workday already records some assistant activity on its own reports. It does not record every read. A connector that stores no Workday rows cannot fill that gap with a copy of the payload.

[Kiweely Bridge](https://kiweely.com/bridge) (coming next) is the user-delegated case in this guide: each call runs as the worker who signed in. Workday’s own agents are the other case: an agent system user, with or without a person beside it. The reports are different. Neither report is a full transcript of the chat.

## Trail A: Workday’s own agents

[Agent Security](https://doc.workday.com/admin-guide/en-us/workday-ai/agent-security/concept--agent-security.html) says the audit log distinguishes an agent acting alone from an agent acting for someone:

| Mode | What the audit shows |
| --- | --- |
| Delegate | The agent account is **By User**. The person is **On Behalf Of User** |
| Ambient | The agent system user is **By User**. There is no person in that row |

The report named for this is **View AI Agent User Audit Trail**, secured to the **Reports: AI Agent Security** domain. **View Security for Agent Skill** shows the domain and business-process policies on a skill’s tools. [About Workday Agents](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/setup-considerations--agent-system-of-record.html) adds:

-   **All AI Agent Accounts** (Workday Accounts domain) lists the agent system users.
-   **Agent Input and Output Request Details**, **Generate Agent Input and Output Report**, and **Input and Output Report For Registered Agents** are secured to **Agent Compliance** and, on that page, are only available for Workday-built agents.
-   The **Agent Input and Output Details** data source covers the past 30 days and is also under Agent Compliance.
-   Several session and unique-user reports are only for Workday-built agents.
-   Workday recommends examining the audit log regularly. A Sandbox refresh does not delete usage activities from previous weeks.

If you are correlating a Workday-built or external agent, start with **View AI Agent User Audit Trail** and the agent account, then the person in **On Behalf Of User** when the skill is delegate. Do not expect the Workday-built-only input and output reports to contain an outside assistant.

## Trail B: a person using Workday, including a user-delegated connector

[Reference: Auditing-Related Reports](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/auditing/wln1467042699742.html) is the general catalog:

| Report | What it is for | Domain called out on the page |
| --- | --- | --- |
| Update Audit | Sign-on and sign-off, password changes, invalid passwords, data added or deleted, and business-process transactions, for a worker or non-worker | System Monitoring, and Update Audit CustomerSupport |
| View User or Task or Object Audit Trail | Changes by a combination of Workday account, transaction, and business object over a period you set | System Auditing |
| View Worker History | Business processes and actions that affect a worker, including hire, compensation, and personal-data changes. Contingent-worker history is included when it exists | Self-Service: Historical Staffing Information, and Worker Data: Historical Staffing Information |
| View Audit Trail | Changes in Workday over a period | System Auditing (and a Customer Central domain) |

**Signons and Attempted Signons** is a sign-in report. Workday’s mobile authentication topic points administrators at it to troubleshoot sign-in. It is not a line per question the assistant asked.

A user-delegated connector does not create a second worker. The business process still shows the worker who submitted it, because Workday ran it as that account. That is the join key for writes: worker, task, and time on Update Audit or View Worker History.

## What Workday says it does not log

[Integrations, EIB, and Web Service Limits](https://developer.workday.com/documentation/dan1370797408285/ReferenceIntegrationsandWebServiceLimits) states that Workday does not log GET requests or unsuccessful web-service requests, and that Workday does not log web-service responses. You can send external integration HTTP headers if you need those calls in server logs. The page does not say those headers appear on Update Audit.

Read-only questions are the hole. A WQL read or a REST GET can answer the employee and leave no business-process row, because nothing changed. An unsuccessful call can be missing too. Correlation for those calls is not “find the payload in Workday.” It is “this worker was signed in, this task was or was not submitted, and the connector’s own metadata shows a tool name and a status at this time.”

## What a zero-payload connector can add

Kiweely Bridge (coming next) publishes a narrow log on purpose. Structured telemetry records timestamp, tenant ID, tool name, HTTP status, and latency. Request arguments, WQL rows, worker names, and pay figures are not serialized to logs or traces. There is no database of employee Workday credentials to join on later. An idle worker holds none of those grants; each grant is sealed and decrypted only in memory for the call.

Use the two trails like this:

| You want | Look here | Do not expect |
| --- | --- | --- |
| Who an agent system user acted for | View AI Agent User Audit Trail | A row for every read, or input and output text for an outside assistant |
| Which worker submitted a change | Update Audit, View Worker History, the business process | The chat transcript |
| Whether a read happened | The connector’s tool name, status, and time, plus the worker’s own session if you have it outside Workday | The worker’s name inside Bridge’s telemetry, or the WQL text inside Workday’s response log |
| A stored copy of the answer | Nowhere on the Bridge design | Bridge to retain prompts or Workday rows |

Keep clocks in one zone when you compare. Workday’s web-service date-time guidance on the limits page says returned datetimes are in Pacific Time. Bridge’s published field is a timestamp without a stated zone on the security page, so confirm the zone in the tenant’s export before you call two rows the same event.

## A check that does not depend on the assistant

1.  Pick a write you enabled and a read you only queried.
2.  Submit the write as a test worker in a non-production tenant. Confirm the business process names that worker.
3.  Run the read. Confirm you do not invent a Workday row that the GET-logging rule says will not be there.
4.  Match the write by worker and time. Match the read by tool name, status, and time in the connector metadata, knowing the worker’s name is not in that metadata.

[Register interest](https://kiweely.com/bridge) if you want that user-delegated shape. Kiweely Bridge is coming next.

## Frequently asked questions

### Does every assistant call show up as the employee?

On a user-delegated call, Workday applies that employee’s security, and a business process they submit is theirs. On a Workday agent in delegate mode, the audit row is the agent account as **By User** and the person as **On Behalf Of User**. Ambient mode records the agent account only.

### Can we reconstruct the question from Bridge’s logs?

No. The published telemetry has no prompt, no worker name, and no Workday row. That is the point of the design, and it limits forensics to tool name, status, latency, tenant, and time.

## Sources checked

-   [Agent Security](https://doc.workday.com/admin-guide/en-us/workday-ai/agent-security/concept--agent-security.html)
-   [Reference: Auditing-Related Reports](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/auditing/wln1467042699742.html)
-   [About Workday Agents](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/setup-considerations--agent-system-of-record.html)
-   [Integrations, EIB, and Web Service Limits](https://developer.workday.com/documentation/dan1370797408285/ReferenceIntegrationsandWebServiceLimits)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Separating Production and Sandbox Workday Endpoints So Demos Miss Live Workers Workday gives every tenant its own URL. Production holds live data. Sandbox and Sandbox Preview are typically copies of it. Implementation tenants and the sample-data demonstration tenant are the safer demo targets. A user-delegated connector follows whichever URL the person signs in on.](https://kiweely.com/guides/separate-production-and-sandbox-workday-endpoints)
-   [### Scoping AI Workday Access for Contingent Workers and Alumni Contingent Worker as Self and Employee as Self are limited to the person’s own data. Terminee as Self is the self-service group for terminated workers. Former Worker Storage is a different population. A user-delegated assistant cannot see more than that sign-in already can.](https://kiweely.com/guides/scoping-ai-workday-access-contingent-workers-alumni)

### More guides on More Workday guides

[All 46 guides](https://kiweely.com/guides#more)

-   [Workday Cost Centers and Workers to NetSuite After a Reorg](https://kiweely.com/guides/workday-cost-centers-workers-to-netsuite)
-   [Workday Headcount to Snowflake When Data Cloud Is Not Enough](https://kiweely.com/guides/workday-headcount-to-snowflake-beyond-data-cloud)
-   [Performance Check-In and Goals Screens Managers Will Open](https://kiweely.com/guides/performance-check-in-goals-screens-managers-open)
-   [Building an Open Enrollment Decision Screen on Live Workday Elections](https://kiweely.com/guides/open-enrollment-decision-screen-live-workday-elections)
-   [Mandatory Learning and Acknowledgements with Live Workday Status](https://kiweely.com/guides/mandatory-learning-acknowledgements-live-workday-status)
-   [Day-One Tax, Payment Election, and Form I-9 Pages as Pass-Through](https://kiweely.com/guides/day-one-tax-payment-i9-pass-through-pages)
-   [Compensation Statement Screens and Peer Pay Redaction](https://kiweely.com/guides/compensation-statement-field-redaction-manager-peers)
-   [Publishing One Employee Screen to Web, Teams, and Phone](https://kiweely.com/guides/one-screen-definition-web-teams-phone)

### From the blog on More Workday guides

[All posts](https://kiweely.com/blog)

-   [Answering New Hires’ First-Week Workday Questions in ChatGPT, Claude, or Gemini](https://kiweely.com/blog/onboarding-new-hires-answering-first-week-workday-questions)
-   [Giving Employees a Better Workday Experience in Days Without a Six-Month SI Project](https://kiweely.com/blog/modernizing-employee-workday-experience-without-six-month-si-project)
-   [Giving Hiring Managers Live Workday Open Roles and Headcount Answers in Chat](https://kiweely.com/blog/live-headcount-open-requisitions-answers-for-hiring-managers)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
