tools/list is the menu the model is allowed to see. It is not the security decision. Workday still allows or denies the call. A role-safe menu is one that does not advertise an HR Partner task to every employee who shares the connector.
Kiweely Bridge is coming next. The published design is one tool list per tenant: the admin chooses which reads, reports, fields, and writes exist, and disabled writes are absent from the list. The trust table says the assistant sees only the tools published for that tenant. It does not say Bridge emits a different tools/list document for each security group. Role safety is that published list, plus Workday’s check on every call, plus field redaction. Plan the list for the broadest group that will be offered the connector.
What the two roles already mean
Security Group Membership defines the difference the catalog has to respect:
| Employee as Self | HR Partner | |
|---|---|---|
| Membership | Employee as SelfWorkday-assigned | HR PartnerDerived from a role on a position or job |
| Constraint | Employee as SelfThat employee’s own data | HR PartnerTarget data in the organizations where the role is assigned |
| A tool that reads “a worker’s compensation” | Employee as SelfLegitimate only for themselves, and only if a self-service compensation domain is granted | HR PartnerLegitimate only inside those organizations, and only if the worker-data domain is granted |
| A tool that searches the population | Employee as SelfA standing temptation for the model to ask for people this group cannot see | HR PartnerStill constrained. An unconstrained HR group is a different security group, and the education manual treats unconstrained role-based groups as the exception you configure on purpose |
Workday will deny the row. The model may still try the tool, burn a round trip, and tell the employee the tool exists. That is the failure role-safe catalogs are meant to avoid. Denial is the backstop, not the menu design.
On a company Claude, ChatGPT, or Gemini plan, an owner adds the Bridge connector once. One URL makes the “offer HR tools to everyone and let Workday sort it out” shortcut more attractive. It is the wrong shortcut if employees and HR Partners share that workspace.
What each catalog should contain
These are categories, not tool names. Bridge does not publish a fixed Workday tool schema in advance of your tenant’s reports. Names like a specific WQL alias belong to your tenant after discovery, not to this article.
Employee as Self, on the shared connector
- The person’s own time, pay, benefit elections, and personal data, where those self-service domains exist.
- Their own goals, review status, or learning record only if you have tested that read as Employee and it returns one worker: them.
- No worker search, no “compensation by organization,” no talent pool, no report whose default is the supervisory organization tree.
- No writes, until you enable one task and you have watched the browser card. Requesting time off is the example the Bridge pages use. It is still off until you enable it.
HR Partner, if you truly need those questions
- The same self-service reads, so partners can ask about themselves without a second product.
- Reads that match domains they already have, tested as that partner, limited to the organizations where the role is assigned. A partner for one supervisory organization who receives another organization’s workers has a Workday constraint bug, not an assistant success.
- Population reports only when the report’s own prompts are required and a persona test shows the extra organizations are absent.
- Writes even more rarely. The browser card shows now and after for that change. It does not make an HR Partner into a shared service account.
If those two lists are different, do not merge them onto the one connector every employee will add. The published pages do not describe automatic per-role menus. Splitting the audience is an admin choice: a connector whose list is safe for Employee as Self, and a separate published list for HR only if and when the product supports a second policy. That second policy is not a line item on the price page. Ask when you register. Until it is explicit, ship the employee-safe list only.
The AI admin agent’s job, as published, is to test prompts as Employee, Manager, and HR Partner before production. A test that succeeds only as HR Partner means the tool does not belong on the employee connector.
A tools/list review you can do without the product
When Bridge is available, read the list the assistant actually received. Coming next means you cannot do that on a production company tenant today. The review criteria:
| Check | Employee connector | HR connector, if you have a separate one |
|---|---|---|
| CheckWrites | Employee connectorAbsent, or a single enabled task you named | HR connector, if you have a separate oneOnly tasks that role can initiate |
| CheckArguments that take a worker ID | Employee connectorDefault to the signed-in worker, or do not exist | HR connector, if you have a separate oneRequired, and tested across an organization boundary |
| CheckReports | Employee connectorThe person’s own data | HR connector, if you have a separate oneThe partner’s organizations only, confirmed with a worker outside that scope |
| CheckFields | Employee connectorAdmin redaction still applied in memory | HR connector, if you have a separate oneSame. Redaction is not a reason to skip the domain |
| CheckDenial test | Employee connectorEmployee asks for a coworker’s pay and gets Workday’s denial, and the tool was not required to discover that | HR connector, if you have a separate onePartner asks outside their organizations and gets the same |
Workday’s agent skills have a similar two-step check, if you use that path instead: Available To on the skill, then the person’s domains. Bridge is not that registration. Do not copy an agent-skill allow-list into a Bridge tool list and assume the gates match.
Frequently asked questions
If Workday denies the call, why hide the tool?
Because the model offers what it can see. A denial after the offer still taught the employee the tool’s name and spent a call on the tenant. Hiding it is how the shared connector stays honest.
Does the HR Partner catalog cost more?
The published price is per company by licensed employees: $499, $1,499, or $3,999 a month, unlimited calls, not per role and not per tool. Above 20,000 employees is a quote. A second policy is not a published SKU. Register interest and describe the two audiences. Kiweely Bridge is coming next.