Workday Community is part of the product’s own instructions. The Deployment Agent setup topic tells you to open your Community profile and read Subscription Service Agreement so you know whether you are on UMSA or still on MSA. That is a fact about your contract. A configuration reply under a Community thread is a fact about someone else’s tenant until you prove it in yours.
Deployment Agent can inspect configuration when you are in Implementation, Preview, Sandbox, or Customer Central connected to non-production, and when Tenant Inspection is on. It is not available as a Production assistant. Chat history there lasts 14 days and does not cross tenants. None of that makes a Community post authoritative.
What to lift out of the post before you ask the tenant
Copy only objects you can search for:
- A task or report name.
- A domain name.
- A business object and a field.
- A web service operation and the exact fault text.
- A security group type (role-based, user-based), not a person’s name.
Drop tenant nicknames, “we just did this in Production,” and screenshots you cannot map to a task. If the post has no object name, it is not ready to verify.
Ask with the marker Workday says is required
The sample-prompts topic says the agent has no indicator that Ask is enabled. Phrases like in my tenant are how you push it toward your configuration. In Customer Central, name the connected tenant or you may inspect the wrong one.
Security posts map cleanly onto the published Ask example. Replace the field and the role. Keep the three questions: which domain, who has View, how to update.
I am a Workday security administrator. In my tenant, users assigned to the [role] cannot view the [field] on worker profiles. Please look in my tenant and inspect our security configuration to explain which domain security policy controls access to this field, which security groups currently have View access, and how to update the policy.
Calculated-field posts:
In my tenant, how does this calculated field work: [Calculated Field]
Report posts, Customer Central form from the same sample table:
In my [tenant name] tenant, show me all custom reports created by [User/Security Group].
A definition with no tenant marker is allowed when you only want the concept. The published learning prompt asks for layperson’s terms and bullet points. Use that for “what is a condition rule,” not for “why did our step skip.”
Decide what the tenant said
| Community claim | Tenant check | Stop if |
|---|---|---|
| Community claim“Add this group to the domain.” | Tenant checkOpen the domain. Confirm the field is on that policy. | Stop ifThe domain name does not exist, or the field is on a different policy. |
| Community claim“Use this calculated field in eligibility.” | Tenant checkCalculated fields can be condition rules. Workday says they cannot be eligibility rules. | Stop ifYou were about to follow the post onto eligibility. |
| Community claim“Put Initiator on the first step.” | Tenant checkOn initiation, Initiator returns no results because the process has not started. | Stop ifThe post is describing a later step and you pasted it onto initiation. |
| Community claim“The step should have errored.” | Tenant checkIf the processing user cannot see the next step’s fields, the step is skipped. | Stop ifYou expected an error and the skip is the documented behavior. |
| Community claim“This SOAP parent field is the bug.” | Tenant checkWorkday’s SOAP example says a parent-element fault can be a missing child or security. | Stop ifYou “fixed” the XML by repeating a parent element that was already there. |
| Community claim“Do this in Production chat with Deployment Agent.” | Tenant checkThe setup topic says it is not accessible for use in Production. | Stop ifYou were about to test the post in Production because Community said it worked there. |
After you apply a step that was right, use thumbs up or thumbs down. Thumbs down does not edit Community, and it does not undo an activated security change. Activation is Activate Pending Security Policy Changes.
When you cannot use the agent
You can still verify. The agent is a faster way to get a tenant-grounded suggestion when Ask is on. The source of truth is the task:
- Domain: Edit Security Policy Permissions and the securable items on that policy.
- Field: Create Calculated Field or View Calculated Field, and Business Object Details.
- Process: Rule Tester on an event. It is not available for Workday-owned rules.
- Agreement: the Community profile path in the setup topic, which is about UMSA versus MSA, not about another customer’s business process.
If Deployment Agent is not registered, or your user is not on Deployment Agent Users, do not paste the Community thread into a personal chat as a substitute. That copies tenant detail out of Workday. The admin guide’s path is the agent inside the non-production tenant, or the tasks themselves.
Write the result back in one paragraph
“Community said [object]. In [tenant], the domain or field or rule shows [what you opened]. We [activated / did not activate]. Rule Tester or the domain screen [matched / did not match].”
That paragraph is the design note. The thread is not.
Frequently asked questions
Does Workday say Community answers are wrong?
No. Community is where Workday sends you for the agreement type, and customers discuss configuration there. This article says a reply becomes your configuration only after you see it in your tenant.
Can the agent read the Community thread if I paste it?
You can paste a question. Inspection still depends on “in my tenant” and on Tenant Inspection. A pasted thread without a field name is Context without an Action. CRAFT wants the task stated: which domain, which field, which fault.
What about answers that cite an old release?
Your tenant’s task labels win. If Create Calculated Field does not offer the function the post names, do not recreate it under another function name and call it the same design.
Should we reply on Community with our tenant’s domain list?
Not with worker data, and not with a dump of security groups. If you confirm a task name that matches the admin guide, that is a product fact. Your Available To groups are your tenant.
Sources checked
Workday admin-guide pages in the frontmatter, fetched 2026-11-16. Community itself is not a source host for a step-by-step configuration claim in this piece.