Kiweely Bridge connects Claude, ChatGPT, and Gemini to a Workday tenant for every employee. It is coming next. The setup Workday actually gives you is the Register API Client task, secured by Security Administration in the System functional area. Bridge’s product page says the client is an Authorization Code Grant with PKCE, that every call runs as the signed-in worker, and that you do not register an Integration System User or use Register API Client for Integrations.
An AI admin agent on the Bridge page walks a Workday admin and an IT admin through Sandbox: it prepares functional areas and web-service-enabled custom reports, and it waits for a yes before that configuration is the one you keep. This article is the checklist you use while you click. It does not paste client secrets, and it does not invent a redirect address.
What the product says the admin agent will put in front of you
- You say what employees should be able to ask. The published Sandbox example is PTO, pay slips, directory, org chart, and requesting time off.
- The agent checks functional areas. The walk-through names Staffing, Absence, Payroll, and System.
- It prepares Register API Client settings: Authorization Code and PKCE.
- It verifies the self-service reports it found. The walk-through cites Self-Service: Time Off, Self-Service: Pay, and two RaaS reports.
- You confirm. The page says it waits for your yes.
- You choose which tools, reports, and fields exist. The tenant starts read-only. A write is enabled one by one, and each enabled write pauses for a browser card that shows the current value and the value after the change. Disabled actions are not offered to the assistant.
- It runs boundary checks in Sandbox as Employee, Manager, or HR Partner before anyone gets a link.
- You publish a connector URL, or you export a stateless container for your own cloud. On a company plan for Claude, ChatGPT, or Gemini, a workspace owner adds the connector once. Employees sign in on Workday as themselves.
The page also says Bridge does not need Agent System of Record and does not need an extra Workday AI SKU. That is the opposite of Workday’s path for registering an external agent in ASOR, which uses Register API Client scoped to the Agent System of Record functional area and requires Setup: Agents. Do not reuse an ASOR client as the Bridge client. The scopes are for different products.
What you will see on Workday’s Register API Client task
Two Workday procedures show the same task with different scopes. Use them as the field list, not as the scope list for Bridge.
Time Kiosk registration, which is the public procedure that turns on PKCE:
| Option | What that procedure selects |
|---|---|
| OptionClient Name | What that procedure selectsA unique name. |
| OptionClient Grant Type | What that procedure selectsAuthorization Code Grant. |
| OptionSupport Proof Key for Code Exchange (PKCE) | What that procedure selectsSelected. |
| OptionAccess Token Type | What that procedure selectsBearer. |
| OptionRedirection URI | What that procedure selectsAn address for that app. The kiosk procedure uses a Workday kiosk address. That address is for Time Kiosks, not for Bridge. |
| OptionScope (Functional Areas) | What that procedure selectsTime Tracking, in the kiosk procedure. |
External-agent registration uses the same task, Authorization Code Grant, Bearer, a redirect URI, scope Agent System of Record, and Include Workday Owned Scope. The person registering needs Setup: Agents. That is the ASOR API path. Bridge’s page says not to use that pattern and not to use an integration system user.
For Bridge, confirm three things against the product page before you save the client:
- Grant type is Authorization Code, and PKCE is on, matching the prepared settings in the walk-through.
- Functional areas are the ones the admin agent showed you (the example set is Staffing, Absence, Payroll, and System), not “every area in the tenant,” and not Agent System of Record unless you are separately registering a Workday external agent.
- The redirect is the one the admin agent prepared. Do not type the Time Kiosk redirect because it appeared in a Workday example.
Workday’s kiosk topic says you share the client ID with the person finishing setup. Bridge’s page does not tell you to email a client secret to employees. Employees sign in on Workday. Keep the credential material with the admins who confirmed the client.
Reports the assistant will call
Bridge’s page includes custom RaaS reports. Workday’s RaaS topic: only advanced and search reports become web services, the caller still needs a tenant account and permission to the report and the data, and the report owner’s username cannot contain a backslash. Copy a standard report before you enable it if an integration or an assistant will depend on it. Namespace changes break callers. CSV column order can differ from the report. Agree which reports are in the “two RaaS reports” set before you leave Sandbox.
Read-only is the default. A report that was safe to run in Workday is still subject to the worker’s security when the assistant calls it. The boundary test as Employee, Manager, and HR Partner is the check that a manager prompt cannot read another organization. Bridge’s page says it never calls Workday with an integration system user, so Workday applies the same domain and organization security as the web app. An admin policy can narrow that further. It cannot widen it past Workday.
Hosting and price, so the API client is not the only decision
On Kiweely Cloud, responses pass through memory so fields you blocked can be removed. The page says Workday records, prompts, and answers are not written to disk, databases, or logs. Teams that do not want that hop can self-host the stateless container.
Price is per company, by licensed Workday employees, unlimited calls, Production and non-production tenants included: $499 a month up to 1,000 employees, $1,499 from 1,001 to 5,000, $3,999 from 5,001 to 20,000, and a quote above that or for a dedicated static IP or self-hosted container. One person can use Bridge free on their own Workday developer tenant and its sample data. There is no card for that tier. A company still implementing Workday pays its band for its implementation tenants.
Because Bridge is coming next, this setup is the decision you rehearse in Sandbox and on a developer tenant. It is not a connector you can hand every employee today.
Frequently asked questions
Can we point Bridge at the API client we already use for Studio?
Only if that client is an Authorization Code grant with PKCE for the functional areas you intend employees to use, and you accept that those employees will be the callers. A client built for an integration system user is the pattern Bridge’s page says it does not use. Prefer a client the admin agent prepared for this purpose. Workday’s external-agent topic recommends a separate client per agent so they stay manageable. The same habit helps here.
Do we have to enable Agent System of Record first?
Not for Bridge. The product page says no. You do need ASOR if you are also turning on Workday-built agents. Those are separate setups. Do not block the API client on ASOR, and do not skip ASOR for Self-Service Agent because Bridge does not need it.
Who clicks yes?
A Workday admin who can run Register API Client, plus the IT owner who will add the connector to the company AI workspace. The employee does not register the client. The employee signs in when they use it.
What if the Sandbox functional areas are wrong?
Do not confirm. The walk-through stops at “ready for your review.” Change the question you asked (“PTO and directory only”) and look at the functional areas again before you create the client in Production.
Sources checked
Kiweely Bridge and the Workday pages in the frontmatter, fetched 2026-11-16. The Time Kiosk redirect is cited only as that procedure’s value, not as Bridge’s.