Security teams often put a gateway in front of Claude, ChatGPT, or Gemini to log prompts, block pasted spreadsheets, or swap models. That gateway is not Workday, and it should not become the path that changes Workday.
Kiweely Bridge is coming next. It assumes the assistant calls a remote connector and the employee signs in on Workday. A gateway you operate in front of the model is your system. These are the boundaries the Bridge pages already draw, and a gateway does not get to redraw them.
What can sit in the gateway
The model conversation: the employee’s words, the tool result the assistant was given, and your own retention of those prompts. Bridge’s published logs do not store prompts or answers. Yours might. If the works council or the privacy notice cares about prompt retention, the gateway is the system to describe, not Bridge’s telemetry. Bridge’s telemetry stays timestamp, tenant ID, tool name, HTTP status, and latency.
Routing among models is also outside Bridge. The product pages name Claude, ChatGPT, and Gemini as the assistants. They do not name a gateway product, and they do not promise that every gateway’s tool protocol will work. Confirm the assistant can still reach the connector URL. Do not assume a custom header your gateway injects is part of the Workday call.
What stays out of band
| Step | Where it happens | Why a gateway must not take it over |
|---|---|---|
| StepWorkday password and MFA | Where it happensWorkday’s own sign-in screen | Why a gateway must not take it overBridge never sees them. A gateway that asks employees to paste a Workday password is a new incident, not a control |
| StepThe Workday grant | Where it happensSealed with AES-256-GCM inside the client token, decrypted in Bridge’s memory for the call | Why a gateway must not take it overThe assistant cannot decrypt it. The gateway should not be given a decoder, a refresh-token store, or a shared integration password “so the model can skip sign-in” |
| StepWhich writes exist | Where it happensAdmin policy. Disabled tasks are missing from the tool list | Why a gateway must not take it overA gateway prompt that says “call the update anyway” cannot conjure a tool the server did not list |
| StepThe approval | Where it happensA browser card, outside the chat, showing now and after. The employee clicks Allow | Why a gateway must not take it overChat text cannot click Allow. A gateway is still chat-side. It must not auto-approve, replay an old approval, or turn “yes” in the transcript into the click |
| StepThe pending write | Where it happensA short-lived action hash until the browser approval or expiry | Why a gateway must not take it overThe gateway does not need the hash, and it should not be a second place that can submit the business process |
The trust table on the Bridge security page is blunt about the assistant: it cannot submit a write from chat alone, and it receives status after approval. A bring-your-own gateway is another assistant-side component. Give it the same constraint.
Patterns that look helpful and break the model
“The gateway will hold one Workday service account.” That is an integration system user. Bridge’s FAQ says it does not use one. Every call is the employee’s grant so Workday enforces the same domains as the UI. A gateway service account is a different product, with a different breach.
“The gateway will approve writes under $0.” There is no dollar threshold on the Bridge pages. The rule is every enabled write, approved in the browser, or not submitted.
“The gateway strips pay fields, so Workday security matters less.” Field redaction in Bridge is in memory, on top of Workday’s domains, configured by the admin. A gateway that only sees the model’s text sees it too late if the tool result already left Workday. Do the domain review in Workday. Use gateway filters as a second net for pasted files, not as the Workday control.
“We will log full tool payloads in the gateway for audit.” You can, because you run it. You will then be storing the HR data Bridge refused to store. Write that down in the briefing. Do not describe the combined system as zero-retention.
A boundary you can hand to the gateway owner
- The gateway may authenticate employees to the assistant.
- The gateway may not collect Workday passwords, MFA codes, or Workday refresh material.
- The gateway may not call Workday except through the employee’s connector session.
- The gateway may not implement an Allow button for Workday writes. That button stays on the Bridge browser card.
- If the gateway stores prompts, say so, and do not cite Bridge’s empty payload logs as covering that store.
Pricing is unchanged by the gateway: $499, $1,499, or $3,999 per company per month by licensed employees, quote above 20,000. The gateway’s own bill is not included. Bridge is coming next. Register interest and describe the gateway you already run, so the connector URL and the out-of-band card are tested with it rather than assumed.
Frequently asked questions
Can the gateway be the browser card?
No. The card is out of band specifically so a prompt, including one that passed through a gateway, cannot approve itself. Moving Allow into the gateway puts it back in band.
Does Bridge support a named gateway vendor?
The pages do not list one. They list the assistants and the rule that writes wait for the browser. Support for a specific gateway is not a published claim.