---
title: "Proxy test after AI Workday changes — Kiweely"
description: "After an AI suggestion changes security or a business process, test as the affected user with Start Proxy and Stop Proxy, then run Rule Tester or Test My Setup."
url: https://kiweely.com/guides/workday-start-proxy-testing-after-ai-changes
---

# Start a proxy test after an AI-suggested Workday change

Workday’s Adaptive Planning proxy procedure uses a proxy policy, Start Proxy, and Stop Proxy in non-production, and records the proxy user. After an AI-suggested security or rule change, add the tester that matches the object you edited.

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

An AI suggestion that names a security group or a condition rule is not tested until someone who is not the implementer runs the task. Workday’s Adaptive Planning proxy procedure is the public, step-level description of how an administrator acts as another user: a proxy access policy, the **Start Proxy** task, work on behalf of that user, then **Stop Proxy**. The audit log records the proxy user’s sign-in. The procedure is written for a non-production Adaptive Planning environment. It points to **Concept: Proxy Sessions** for the general session behavior. Read that concept in your admin guide before you proxy into HCM or payroll tasks. This article does not invent extra proxy screens the Adaptive Planning topic does not show.

Security for that procedure is the **Security Configuration** domain in the System functional area.

## What the published procedure actually requires

1.  The proxy user is synced and allowed to sign in on behalf of other users.
2.  A user-based security group contains the people who may proxy.
3.  A proxy access policy names three things: the non-production environment, the group that can proxy, and the group on whose behalf they may act. The topic’s example policy is named Workday Proxy Access policy, with groups Adaptive Planning Proxy Users and Adaptive Planners. Your HCM test needs the equivalent policy for the populations you will impersonate. Do not reuse the Adaptive Planning groups just because the example used those names.
4.  Sign in to the non-production environment as a member of the group that can proxy.
5.  Run **Start Proxy** and choose the user.
6.  Confirm you are on the “on behalf of” welcome experience before you open the task you changed.
7.  Perform the test.
8.  Sign out of the product you opened, if you opened one, then run **Stop Proxy**.

The topic says this is how you validate the implementation for that user without sharing their password. It also says to use the exportSecurityAudit API if you need the audit details. For a functional test, the minimum record is: who proxied, who they proxied as, which tenant, which task, and what the screen did.

## After the AI change, pick the tester that matches the object

Proxy answers “what does this person see.” It does not replace the object-specific tester.

| You changed | Prove it with | Why proxy alone is not enough |
| --- | --- | --- |
| A domain policy the agent told you to edit | Activate pending security policy changes first. Then **Start Proxy** as a user in the group that was added, and as a user who should still be denied. | Pending changes are not live. A test before activation will look like a failure or, worse, like the old correct behavior. |
| A business process condition rule |  **Rule Tester** on a business process event, then proxy as the processing user of the previous step. | The condition-rule topic says that if the processing user cannot access fields or values in the next step, the step is skipped. Your implementer account will not show that skip. Rule Tester is unavailable for Workday-owned rules. |
| An agent skill’s **Available To** group |  **View Security for Agent Skill**, then **Test My Setup** for that group. | Functional status tells you Full Match, Review Required, Config Required, or Not Evaluated. Test My Setup needs Security Administration and shows the policy paths. Proxy can still confirm the person can open the assistant. |
| A calculated field used by a rule | A report row for a worker who should match and one who should fall through, then Rule Tester. | The field’s order (first true condition wins, on Evaluate Expression) is independent of who is logged in. |

The Deployment Agent security example is the kind of suggestion that triggers this routine. The example prompt asks which domain controls Bonus Plan Override and which groups have View. The sample answer names **Worker Data: Compensation Explicit** and says to add Payroll Specialist and activate pending changes. Your proof is: activate, proxy as a Payroll Specialist, confirm the field, proxy as a user outside that group, confirm it is still hidden, **Stop Proxy**.

## Order of operations

Do not start with proxy.

1.  Save the AI answer beside the task you will run. If it named a task you cannot find, stop. Do not guess a similar task.
2.  Make the change in a non-production tenant.
3.  If it was security, run **Activate Pending Security Policy Changes** and confirm.
4.  If it was a condition rule, run **Rule Tester** on an event that should pass and one that should fail.
5.  If it was an agent skill, clear **Config Required** on **View Security for Agent Skill** before you involve a worker.
6.  **Start Proxy** as the affected user. Run only the task in the test plan.
7.  **Stop Proxy** before you proxy as the next user. Overlapping sessions make the audit log ambiguous.
8.  Write pass or fail against the user, not against “the AI was right.”

Initiation rules have a special trap. If the source field is **Initiator** on the initiation step, Workday says it returns no results because the process has not started. Proxying as the worker will not fix a rule that reads Initiator too early. Change the source field.

## What to record

| Field | Example of a complete note |
| --- | --- |
| Tenant | Sandbox, not Production |
| Proxy user | The implementer account |
| On behalf of | A named worker in Payroll Specialist |
| Policy | The proxy access policy that allows that pair |
| Change | Domain Worker Data: Compensation Explicit, View for Payroll Specialist, activated |
| Seen | Bonus Plan Override visible on the worker profile |
| Negative test | A user outside the group, field not visible |
| Stop | Stop Proxy completed |

If you cannot name the proxy policy, you are not ready to test. Sharing a password is the failure mode this procedure exists to avoid.

## Failure modes

| What you see | What to check |
| --- | --- |
| Start Proxy does not list the worker | The policy’s “on behalf of” group does not include them, or you are not in a non-production environment the policy names. |
| The field is still missing after the AI’s fix | Pending security changes were not activated, or you proxied as a different role than the one added to the policy. |
| The step disappears for the manager and not for you | The processing user lacks access to a field that carries its own security. That skip is documented condition-rule behavior. |
| Test My Setup says Not Evaluated |  **Available To** is empty. There is no group to test. |
| Test My Setup says Config Required | A required policy has no groups. Configure that before proxy. |
| You are still “on behalf of” in the next test |  **Stop Proxy** did not run. |

## Watch Kiweely Vine build, secure and test an Extend app

![Kiweely Vine's Training Approval Extend app: the manager opens the employee's training request from his Workday tasks](https://kiweely.com/guides/workday-start-proxy-testing-after-ai-changes/media/vine-extend-app-training-approval-8f3cf9bc75d9.webp)

From the film: the manager opens the employee’s request in his Workday tasks.

From two short messages, Kiweely Vine builds a training approval app in a Workday Development tenant. It sets up the app’s access (Employee As Self and Manager) and the approval’s business process security policy, activates the pending security changes, adds the Manager step to the routing, then tests it as the employees and managers through Start Proxy, privacy checks included. 1 h 51 min from sign-up to the checked result.

[Watch the film (15 min)](https://www.youtube.com/watch?v=hoJV5tq90Ug) · [Start for free](https://kiweely.com/sign-in?intent=signup)

## Frequently asked questions

### Is this procedure only for Adaptive Planning?

The step-by-step policy example Workday published here is for Adaptive Planning, including SAML and user sync prerequisites on that page. **Start Proxy**, **Stop Proxy**, a non-production proxy access policy, and audit logging of the proxy user are the parts you reuse. Confirm **Concept: Proxy Sessions** for HCM tasks before you treat a financial-planning policy as permission to proxy a payroll partner.

### Can Deployment Agent proxy for me?

No published Deployment Agent example says it starts a proxy session. As documented it recommends a domain change; with [Configuration Cloud](https://blog.workday.com/en-us/configuration-cloud.html), in opt-in early access for Workday partners since 18 Nov 2026, it can carry out approved changes. Either way, you run **Start Proxy**.

### Do we proxy in Production to confirm a fix?

The procedure you can cite says non-production. Production confirmation belongs to your change process after the non-production proxy test, not to an AI chat.

### What if Rule Tester and the proxied user disagree?

Trust the proxied user for security visibility and Rule Tester for the condition order. If the tester says the row matched and the user never saw the step, look at the processing user’s field access and at whether security changes are still pending.

## Sources checked

Frontmatter pages, fetched 2026-11-16. Concept: Proxy Sessions is named by the Adaptive Planning topic; this guide does not add steps from an unfetched page.

## Sources checked

-   [Steps: Set Up Proxy User Access to Adaptive Planning](https://doc.workday.com/admin-guide/en-us/adaptive-planning/set-up-adaptive-planning-for-hcm-and-financials/fdj1608585669047.html)
-   [Create Business Process Condition Rules](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/customize-business-processes/dan1370796347209.html)
-   [View Security for Agent Skills and Tools](https://doc.workday.com/admin-guide/en-us/workday-ai/agent-security/view-security-for-agent-skills-and-tools.html)
-   [Example: Troubleshoot Security Policy and Access Configuration with the Ask Skill](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/workday-built-agents/deployment-agent-in-implementation-environments-an/example--troubleshoot-security-policy-and-access-c.html)

## Related guides

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

-   [### Stop or audit a Workday AI agent: an admin runbook When an agent must stop, deactivate it in every tenant where it was set up. Hiding it is not enough if Production will refresh Sandbox. Use View AI Agent User Audit Trail and View Security for Agent Skill to see what it did and what it can still do.](https://kiweely.com/guides/stop-audit-workday-ai-agent-admin-runbook)
-   [### Review security group changes an AI assistant suggested in Workday Deployment Agent can name a domain and a missing View group. As documented, you still edit the policy (change-making is in partner early access), activate pending changes, and confirm View Security for Agent Skill is not Config Required. Constrained groups cannot administer Agent System of Record.](https://kiweely.com/guides/review-ai-workday-security-group-changes)
-   [### Prove an AI-suggested Workday calculated field before it drives a condition rule Deployment Agent’s documented example suggests Evaluate Expression logic for a Worker field and you build it in Create Calculated Field; Configuration Cloud (partner early access) can make approved changes. This guide shows how to prove the field before a rule or integration uses it.](https://kiweely.com/guides/ai-workday-calculated-fields-condition-rules-proof)

### More guides on Tenants and developer accounts

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

-   [When a Successful Payroll File Still Has the Wrong Tax or Garnishment](https://kiweely.com/guides/payroll-files-that-succeed-while-tax-and-garnishment-are-wrong)
-   [What Breaks a Workday Payroll File the Night Before Pay](https://kiweely.com/guides/what-breaks-a-workday-payroll-file-the-night-before-pay)
-   [Separating Production and Sandbox Workday Endpoints So Demos Miss Live Workers](https://kiweely.com/guides/separate-production-and-sandbox-workday-endpoints)
-   [Employee Screen Languages Without Changing the Tenant Default](https://kiweely.com/guides/localization-beyond-one-language-without-tenant-default)
-   [Accessing Employee Payslip Summaries and PDF Payslips Through Workday APIs](https://kiweely.com/guides/workday-payroll-payslip-summary-pdf-retrieval-apis)
-   [How Workday Stores Custom Plan Names, Reason Codes, and Translated Labels Across APIs](https://kiweely.com/guides/workday-custom-labels-translations-reading-tenant-terminology)
-   [Why Workday W-2 Box 1, 3, or 5 Wages Don’t Match Payroll Summary (and How to Fix Them)](https://kiweely.com/guides/workday-w2-box-mismatch-adjust-tax-balances)
-   [How to Customize the Workday Home Page, Daily Brief, and Global Navigation Sidebar](https://kiweely.com/guides/workday-configurable-home-page-daily-brief-setup)

### From the blog on Tenants and developer accounts

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

-   [The Production tenant problem: why AI and enterprise systems need a trust layer](https://kiweely.com/blog/production-tenant-trust-layer)
-   [Workday Testing Tools Compared: Kiweely Vine vs Kainos Smart Test, Opkey and Tricentis Tosca](https://kiweely.com/blog/workday-testing-tools-compared)
-   [Why Workday Community answers fail you—and how to verify in the tenant](https://kiweely.com/blog/workday-community-answers-verify-in-tenant-method)

## 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.
