A security workshop decides who can see and do what. Workday’s model for that decision is three parts: functional areas, security policies, and security groups. Deployment Agent with Ask can inspect how a non-Production tenant implements that model for a field or a task. As Workday documents it, Ask does not grant the access. You edit the policy and run Activate Pending Security Policy Changes.
Workday has not published a security-workshop product. The meeting is yours. The policy is Workday’s.
Two policies, and the workshop has to name which
| Policy | What it decides | HCM course wording |
|---|---|---|
| PolicyDomain security policy | What it decidesWho can view or modify the tasks, reports, and data secured to that domain | HCM course wordingCustomers cannot change the delivered domain or the items secured to it. They put security groups on the policy. |
| PolicyBusiness process security policy | What it decidesWho can initiate, approve, delegate, cancel, and otherwise act, for every definition of that business process type | HCM course wordingOne policy for the type. Definitions can route steps only to groups the policy allows. To do steps can be assigned to any active group, but a task on the to do still has to be allowed to that group. |
Putting a group on a business process step does not let them see a compensation field. Putting them on a domain does not let them approve the hire. The workshop writes two lines for every role.
Payroll’s setup topic is the same pattern, with payroll-specific group types: role-based (a payroll partner sees tasks and data for the pay groups they support), segment-based (decentralized administration of payroll business processes), and user-based (a payroll administrator unconstrained across pay groups). View is typical for reports. Modify includes the tasks and reports on the domain. Third parties can be brought in through service centers, with limited access to a subset of workers, and those representatives are not workers.
Who may use the agent in the workshop
Only groups on the Deployment Agent Users domain, with View on report and task permissions, and on the Ask skill’s access list. Workday’s example group is Implementers. A group on the skill but not on the domain fails validation. Activating the agent is a separate switch in Agent Management Hub.
That access is not a license to show every workshop attendee the agent. The agent reads configuration in the active non-Production tenant, or a named connected tenant from Customer Central. It is not a Production assistant. Chat is deleted after 14 days. Do not put employee data questions into a thread you cannot retain; ask about the policy, not about a named worker’s pay.
There is no indicator that Ask is on. Before the workshop, ask for five calculation fields and open them. If you need a security answer, use the published shape:
I am a Workday security administrator. In my tenant, users assigned to the [role] cannot view the [field] on worker profiles. Look in my tenant and tell me which domain security policy controls the field, which security groups currently have View, and how to update the policy.
Workday’s illustration uses Payroll Specialist and Bonus Plan Override, and describes a result on Worker Data: Compensation Explicit with the role missing from View. Treat that as the shape of an answer. Confirm the domain on your tenant before anyone edits. From Customer Central you can ask how activating the change would affect another implementation tenant. That question is an impact question, not a migration.
A two-hour workshop that ends in an activated policy
First half hour, vocabulary. Use knowledge discovery if the room does not share terms. One new chat, lay language, bullets. Copy the terms into the decision record. Do not design in that thread.
Next hour, one role, one field, one action.
- Name the functional area. For HCM the course lists Staffing, Core Compensation, Organizations, and Personal Data. For payroll, open Domain Security Policies for Functional Area and pick the payroll area rather than guessing the domain name.
- Run the prompt above. Write down the domain it names.
- Open the domain. View Domain, then Edit Security Policy Permissions. See whether the group is on View or Modify.
- If the business process is also in scope, open Business Process Policy > Edit and see whether the group can perform the action. Remember you cannot usefully edit the definition’s secured step until the policy allows the group, and you must activate pending changes before the definition edit will see them.
- Decide in the room: View, Modify, or neither. Say the pay-group or organization constraint if the group is role-based or segmented. Unconstrained user-based groups see all instances of what the policy secures. That sentence should be said out loud before you grant one.
- A security administrator makes the edit in the Implementation or Sandbox tenant and activates it. A second person in that group opens the field or starts the action. That opening is the test. The chat is not.
Last half hour, migration impact. If this policy will move with Object Transporter, say how. Ordinary modified instances are overwritten on the target. Security policies merge unless you choose to overwrite. A security group’s business process security policy permissions migrate additively and do not remove groups already on the target. The workshop’s “revoke” decisions need a manual step on the target, written down now.
Prompts for the three decisions people mix up
| Decision | Prompt | Confirm in |
|---|---|---|
| DecisionWho can see a field | PromptThe published security prompt, with your role and field, plus “in my tenant.” | Confirm inThe domain policy’s View rows. |
| DecisionWho can act on a process | Prompt“In my tenant, which security groups can initiate and approve [business process type]? Which groups are on the step of the definition for [organization]?” | Confirm inThe business process security policy and the definition. |
| DecisionWho can use the agent | PromptDo not ask the agent to list its own access as a substitute for setup. | Confirm inDeployment Agent Users, the Ask access list, and View Security for Agent Skill. |
Failure modes
- Editing a copy of the policy in a chat and never activating. Nothing changes for the user until activation.
- Granting Modify when the room asked for a report. Modify includes the tasks on the domain.
- Using an unconstrained payroll administrator group to solve a “this pay group only” problem. Role-based or segmented groups exist for that constraint.
- Believing a to do assignment grants the underlying task. It does not.
- Migrating the policy and assuming Production groups disappeared. Additive migration will not do that.
- Workshop notes that exist only in the agent. Fourteen days is the retention. Write the domain, the group, View or Modify, and the activation comment into the project record the same day.
- Running the workshop in Production through Deployment Agent. You can configure the agent in Production so Sandbox refreshes keep it. You cannot use it there as a conversational assistant.
Frequently asked questions
Can Ask change the policy if we approve the suggestion?
Workday’s security example ends with you editing the policy and activating changes. Follow that. The concept topic calls the inspection read-only. Workday’s Configuration Cloud, in opt-in early access for partners since 18 November 2026, lets Deployment Agent carry out changes once a plan is approved; that is not what the Ask example shows.
We use implementers in Sandbox. Is that our security design?
No. Implementer groups are how you grant Deployment Agent and build access. The design is the groups your workers will have in Production. Test with a user in the worker’s group before you call the workshop done.
How do service-center users fit?
Payroll’s topic says they are not workers, they have limited tenant access, and they support a subset of workers. Put that in the matrix as its own row. Do not model them as employees.
What do we compare across tenants?
Tenant Compare can compare domain security policies, including whether a domain is suspended because its functional area is disabled, and subdomain differences on a matching parent. Use it after you migrate. Do not use a chat as the compare.
Sources checked
Public Workday topics listed above, fetched 2026-11-16.