The conversation as Vine shows it: the request and every message Vine wrote. Every action Vine took in Workday is in the full screen recording of the run.
Tester (as the consultant) (14:50:43 UTC)
In our Workday tenant, create a user-based security group called “Comp Auditors TT-KV” 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 make the change in our Development tenant.
Kiweely Vine (14:53:52 UTC)
Checking Workday’s own guidance on user-based security groups and activating security changes before I touch the tenant.
Kiweely Vine (14:54:35 UTC)
Now checking the Development tenant for Logan McNeil, the domain, and whether a group with that name already exists.
Kiweely Vine (14:55:19 UTC)
I’m opening the Development tenant in the browser to confirm the domain and Logan McNeil’s account before I ask you to approve the security change.
Kiweely Vine (14:57:09 UTC)
Signed in as Logan McNeil in the Development tenant. Looking up the domain now.
Kiweely Vine (14:57:52 UTC)
The domain exists and the group name is free. Workday security changes need your explicit go-ahead before I make them, even in Development.
Kiweely Vine (15:00:04 UTC)
Approved. Opening Create Security Group in the browser.
Kiweely Vine (15:01:28 UTC)
Create Security Group is open. Filling in the type and name now.
Kiweely Vine (15:02:39 UTC)
The group is created. Next, adding Logan McNeil as a member.
Kiweely Vine (15:09:35 UTC)
Assign Users is open; searching for Logan McNeil’s account.
Kiweely Vine (15:10:01 UTC)
Logan McNeil is now a member. Next, editing the “Worker Data: Compensation” domain’s security policy.
Kiweely Vine (15:11:03 UTC)
Opening the domain’s Edit Security Policy Permissions from its related actions.
Kiweely Vine (15:11:48 UTC)
The policy editor is open. Its permission rows already include groups with Modify, so I’ll add a separate View-only row for the new group.
Kiweely Vine (15:13:15 UTC)
View is ticked and Modify is not. Two alerts came up, so I’m reading them before saving.
Kiweely Vine (15:13:23 UTC)
Both alerts are just Workday’s reminder to activate the change afterwards. Saving the policy now.
Kiweely Vine (15:14:00 UTC)
All seven pending policies are from this one save (the domain plus child policies that inherit from it), with nothing else waiting. Running Activate Pending Security Policy Changes.
Kiweely Vine (15:14:40 UTC)
Workday lists the activation task in this tenant as “Activate Pending Security Policy Changes (Do Not Use)”. Checking what that label means before I go further.
Kiweely Vine (15:15:10 UTC)
Workday’s own text says this older task is being retired and points to the improved “Activate Pending Security Policy Changes” task, so I’m cancelling it and opening the improved one.
Kiweely Vine (15:15:45 UTC)
The improved task lists only the seven policies from this save. Checking the rest of the form for other pending items, then adding a description.
Kiweely Vine (15:16:07 UTC)
Activation completed. Now confirming the result from Workday’s own records.
Kiweely Vine (15:16:34 UTC)
Workday’s records confirm the group, Logan McNeil’s membership and the domain grant, with no changes left pending. Last check: opening the domain’s security policy to confirm the row shows View only.
Kiweely Vine (15:17:45 UTC)
The change is done and active in the Development tenant. “Comp Auditors TT-KV” exists, Logan McNeil (lmcneil) is its only member, and it has View only on “Worker Data: Compensation”.
- Group: I created it as a user-based security group with no restriction to particular organizations. It’s the only group the tenant shows with that name.
- Domain access: I gave the group its own row in the domain’s security policy, with View ticked and Modify left blank. I added nothing under integration permissions, so it has no web-service read or write access either.
- In effect: I ran Activate Pending Security Policy Changes and Workday reported it completed successfully. The only changes waiting were the seven policies from this one save: the domain itself and six related compensation policies that inherit its permissions. Afterwards Workday showed no security policies still pending.
- Readback: The domain’s security policy now lists “Comp Auditors TT-KV” with View “Yes” and Modify blank. Workday’s group records show Logan as the member and the domain as granted. I’ve left that policy page open in the browser.
Three things you should know:
- Inherited access: Six related compensation policies take their permissions from this domain, so the group also gets View there. That includes Compensation Basis, Pay Range, Total Rewards and Market Position Details. This is how Workday handles child policies.
- Activation task: This tenant lists the older activation task as “(Do Not Use)”, and Workday’s own text says it is being retired. I cancelled it without saving and used the newer “Activate Pending Security Policy Changes” task.
- Logan’s access is unchanged: The browser is signed in as Logan McNeil. The new group adds view access for Logan, but it doesn’t take away anything Logan already gets from other groups. So I didn’t test as Logan, because that wouldn’t show what this group alone allows.