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 (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 says the audit log distinguishes an agent acting alone from an agent acting for someone:
| Mode | What the audit shows |
|---|---|
| ModeDelegate | What the audit showsThe agent account is By User. The person is On Behalf Of User |
| ModeAmbient | What the audit showsThe 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 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 is the general catalog:
| Report | What it is for | Domain called out on the page |
|---|---|---|
| ReportUpdate Audit | What it is forSign-on and sign-off, password changes, invalid passwords, data added or deleted, and business-process transactions, for a worker or non-worker | Domain called out on the pageSystem Monitoring, and Update Audit CustomerSupport |
| ReportView User or Task or Object Audit Trail | What it is forChanges by a combination of Workday account, transaction, and business object over a period you set | Domain called out on the pageSystem Auditing |
| ReportView Worker History | What it is forBusiness processes and actions that affect a worker, including hire, compensation, and personal-data changes. Contingent-worker history is included when it exists | Domain called out on the pageSelf-Service: Historical Staffing Information, and Worker Data: Historical Staffing Information |
| ReportView Audit Trail | What it is forChanges in Workday over a period | Domain called out on the pageSystem 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 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 |
|---|---|---|
| You wantWho an agent system user acted for | Look hereView AI Agent User Audit Trail | Do not expectA row for every read, or input and output text for an outside assistant |
| You wantWhich worker submitted a change | Look hereUpdate Audit, View Worker History, the business process | Do not expectThe chat transcript |
| You wantWhether a read happened | Look hereThe connector’s tool name, status, and time, plus the worker’s own session if you have it outside Workday | Do not expectThe worker’s name inside Bridge’s telemetry, or the WQL text inside Workday’s response log |
| You wantA stored copy of the answer | Look hereNowhere on the Bridge design | Do not expectBridge 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
- Pick a write you enabled and a read you only queried.
- Submit the write as a test worker in a non-production tenant. Confirm the business process names that worker.
- Run the read. Confirm you do not invent a Workday row that the GET-logging rule says will not be there.
- 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 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.