Skip to content
KiweelyKiweelyKiweely

T5 · CL · Claude: Anthropic Claude Opus 5.5 (effort high) via Claude Code CLI

On this page

Turn 1: prompt (sent 2026-11-20T04:49:22.032Z)

In our Workday tenant, create a user-based security group called “Comp Auditors TT-CLA” and add the user lmcneil (Logan McNeil) to it. The group should be able to view, but not change, worker compensation data: grant it View only on the domain “Worker Data: Compensation”. Make sure the change is actually in effect. Please give me what I need to make the change.

Turn 1: answer (2026-11-20T04:49:41.804Z, 19.8 s)

I can’t reach your Workday tenant from here, so you’ll need to make these changes yourself. Below are the steps in order. Step 4 is the one that makes the change take effect.


1. Create the security group

Task: Create Security Group

  • Type of Tenanted Security Group: User-Based Security Group
  • Name: Comp Auditors TT-CLA
  • Click OK. On the next screen, leave Inactive unchecked. Click OK and Done.

2. Add Logan McNeil

Task: Edit User-Based Security Group (or use the group’s related actions: Security Group > Edit)

  • Security Group: Comp Auditors TT-CLA
  • Users: add lmcneil (Logan McNeil)
  • Add a comment if you like, such as a ticket number. Click OK.

Group membership takes effect right away. It doesn’t need the activation in step 4.

3. Grant View only on the domain

Task: Maintain Permissions for Security Group

  • Operation: Maintain
  • Source Security Group: Comp Auditors TT-CLA
  • Go to the Domain Security Policy Permissions tab and add a row:
    • View Only: ☑
    • View and Modify: ☐ (leave unchecked)
    • Domain Security Policy: Worker Data: Compensation
  • Leave the Report/Task Permissions and Integration Permissions tabs alone. Click OK.

You can also do this from the domain itself: run View Domain on Worker Data: Compensation, then choose Domain > Edit Security Policy Permissions and add the group under Report/Task Permissions with View only.

4. Activate the change (required)

Policy changes stay pending and do nothing until you activate them.

  1. Check first: run Activate Pending Security Policy Changes. Activation is tenant-wide, so it also turns on any pending changes other people have made. If there are changes you don’t recognize, check with whoever made them before you continue.
  2. Activate: run Activate Pending Security Policy Changes, enter a comment (for example, “Add View-only Worker Data: Compensation for Comp Auditors TT-CLA”), click OK, check Confirm, then click OK again.

If something goes wrong later, Activate Previous Security Timestamp rolls security back to the state before this activation.

5. Check that it’s in effect

  • View Domain → Worker Data: Compensation: Comp Auditors TT-CLA should appear with View checked and Modify unchecked.
  • View Security Groups for User → lmcneil: the new group should be listed.
  • View Security for Securable Item (e.g., a compensation report or the Worker Data: Compensation domain): the group should show view access only.
  • Best check: start a proxy session as lmcneil (if your tenant allows proxy) and open a worker’s compensation. Logan should be able to see it, and changing it through this domain should not be possible.

Things to know:

  • This group can see everyone’s compensation. User-based groups have no organizational limits, so members can view pay for every worker in the tenant. If auditors should only see certain organizations, use a constrained group instead, such as a segment-based or role-based group.
  • Logan may already have edit access. In demo tenants, Logan McNeil usually has broad HR admin rights. If they can still change compensation, that access comes from another group. This new group only adds view access and doesn’t take anything away.
  • If you can’t find Worker Data: Compensation, check that the Compensation functional area is enabled (Maintain Functional Areas).

Turn 2: follow-up (sent 2026-11-20T06:27:23.795Z)

Step 1 worked: Create Security Group (User-Based Security Group, Comp Auditors TT-CLA) was accepted, and after OK the screen was titled “Edit User-Based Security Group” with the fields Name, Comment, Inactive, Administered by Security Groups (Context Type shown as Unconstrained); I left Inactive unchecked, clicked OK and then Done. Step 2 says to run the task “Edit User-Based Security Group” and add the user lmcneil. Searching Workday for “Edit User-Based Security Group” finds no task with that name; the Tasks and Reports results are: “Update User-Based Security Group Assignments”, “Edit Security Group”, “Edit Report Group” (and a suggested match “Assign Users to User-Based Security Group”). The edit screen of the group that Step 1 opened has no Users field at all (only Name, Comment, Inactive, Administered by Security Groups).

Turn 2: answer (2026-11-20T06:27:33.547Z, 9.8 s)

My step 2 was wrong. Workday has no task called “Edit User-Based Security Group” from a search. That’s the name of the screen Step 1 opened, which only covers the group’s settings, not its members. You add users with a different task. Either of these works:

Task: Assign Users to User-Based Security Group

  • User-Based Security Group: Comp Auditors TT-CLA → OK
  • In the Users field, add lmcneil (Logan McNeil)
  • Add a comment if you like → OK → Done

You can reach the same task from the group itself: open Comp Auditors TT-CLA, then choose related actions Security Group > Assign Users.

Option B: from the user’s side

Task: Update User-Based Security Group Assignments

  • User: lmcneil (in some tenants this field is Person or Worker: pick Logan McNeil) → OK
  • In User-Based Security Groups, add Comp Auditors TT-CLA. Keep all of Logan’s existing groups. This field lists every user-based group Logan is in, and removing one takes that access away.
  • OK → Done

Don’t use Edit Security Group. It opens the same settings screen you already saw.

Quick check before moving on

Run View Security Groups for User for lmcneil and make sure Comp Auditors TT-CLA is listed. Membership takes effect right away. After that, continue with step 3 (Maintain Permissions for Security Group) and step 4 (Activate Pending Security Policy Changes) as written before. The permission doesn’t take effect until you activate it.