---
title: "Security Domains for Your First Workday Extend App — Kiweely"
description: "Add a security domain to a first Workday Extend app, secure the business object and the pages, then create and activate the policy in the tenant."
url: https://kiweely.com/guides/first-workday-extend-app-security-domains
---

# Security Domains for Your First Workday Extend App

A security domain file does nothing until you deploy, create the domain security policy, grant a security group, and activate it. Page security should use unconstrained role-based groups. Developer Agent can write the file. It does not configure the tenant.

-   **Checked** against Workday on November 16
-   Applies to **Workday Extend**
-   6 min read
-   Published November 16
-   By Kiweely

A first Workday Extend app is open to every user in the tenant until you secure it. Workday says that directly: by default, any user can access all pages in a custom app. A security domain is how you close that. The domain is a file in the app. The policy is a tenant change you make after deploy. Developer Agent can create the file, including when it scaffolds business objects and security domains from a prompt. The overview says the agent does not configure security. After deploy, you configure it in the tenant.

Skipping the tenant half is the usual first-app failure. The domain looks done in App Builder. HR Administrator still cannot use the data, or, worse, everyone can open the page because you never assigned a domain to it.

## Two kinds of security, and you need both

**Service domain security** is Workday’s existing model for the services your app calls. REST, Graph, WQL, and reports-as-a-service all inherit it. For each service, the endpoint’s documentation lists the domains. On the domain that secures the API, you add a Report/Task permission for the security groups: View for GET, Modify for POST, PUT, PATCH, and DELETE. The service then returns only what that user may read, writes only what that user may write, and returns a permission error otherwise. Your app does not get to bypass that.

**Security domains you create** protect the business objects, business processes, and pages in your app. They are model components. They use the same security groups as the rest of the tenant. Each domain needs a policy for finer control. Creating the component does not create the policy.

Workday’s security concept lists the layers as: domain policies for Workday services, domain policies for model components, authentication for orchestrations, page security, endpoint authentication, and presentation-component visibility. Put the check on the broadest layer that actually covers the data. Do not scatter the same check across every widget if the domain already covers the page and the service.

## Add the domain the way the nomination tutorial does

The names are the tutorial’s names. Use them once so you can see a known-good shape, then rename for your app.

1.  In App Builder, create a Security Domain component named `NominationData`. Domain names must be upper camel case. The label defaults to “My Security Domain”. Change it. Workday uses the label in App Manager and related actions. A first app that ships with that default label is unfinished.
2.  Enable Page Security if this domain should control who can open pages. That property is `enabledForPageSecurity`. Add it only when you mean it. Workday does not apply contextual security to Extend pages. Use unconstrained role-based security groups for page security. Constrained security on a page comes from the endpoint authentication scheme, not from the page domain.
3.  If the same domain should secure orchestrations, also set `enabledForOrchestrationSecurity`. Add that property only when you mean it. You can then put domain security policies on orchestrations.
4.  Create the business object and set its default security domain to this domain. The tutorial uses `Nomination`. An object without a default security domain fails validation with E300.
5.  Save to App Hub, deploy to the development tenant, and open Manage in Tenant.
6.  In App Manager, Configure, find Security Domains, and select Create. Confirm. Add HR Administrator on Report/Task Permissions and check Modify. The tutorial says View and Modify here affect REST API security for the model business object and the pages. Activate Pending Security Policy Changes, enter a comment, and confirm.

Until step 6, the domain file is not a grant. Modify includes the ability the tutorial is aiming at for people who submit nominations. Do not check Modify for a group that should only look. Add a separate View grant for that group.

A worked file, from Workday’s own Add Security Domains page, looks like this when one domain does both jobs:

```
{
  "id": 1,
  "name": "ManageCharities",
  "label": "Manage: Charities",
  "enabledForPageSecurity": true,
  "enabledForOrchestrationSecurity": true
}
```

`id` is an integer greater than zero and less than 32768. Duplicate ids and duplicate names fail E100.

## Page security is not task security

If you assign a security domain to a custom task that opens a page, that domain does not apply to the other pages in the app. Secure each page that needs it. Leaving the default in place means any user in the tenant can open the unsecured pages.

Business processes are different. You can route a business process to constrained security groups. That is the process design, not the page. Do not copy a constrained group onto page security and expect the page to filter by supervisory organization. Workday says the page will not do that.

Delivered APIs stay on their own domains. A Worker prompt on your page still requires the caller to pass the domains documented on that REST endpoint. Your `NominationData` domain does not grant Staffing access. When the tutorial’s worker search returns “Brown”, it is because the connected persona can see those workers under Workday’s own domains.

## What an assistant must not do

-   Generate a domain and stop. The policy is still missing. Put “create and activate the domain security policy” on the test script as a human step.
-   Leave the label “My Security Domain”.
-   Turn on page security and then grant a constrained group. Use an unconstrained role-based group for the page.
-   Add a domain you do not need. A security domain is a model component. App Builder warns that adding one queues promotions to Implementation, Sandbox, and Production until the Friday maintenance window. After it has deployed in a previous version, you cannot remove it. You are allowed to add new security domains to objects and to individual fields later. You are not allowed to delete one that has deployed.
-   Assume the agent registered security because it wrote a skill file. The skill file is for agent registration. Security configuration is the tenant policy.

## Failure modes

-   **Every worker can open the app.** No domain is assigned to the pages. The default is open.
-   **The right group cannot open it.** The domain exists, and Activate Pending Security Policy Changes was never confirmed. App Manager still shows the domain. The policy is pending.
-   **The page opens and the worker search is empty.** Page security passed and the delivered API domain did not. Check the domains named on that REST endpoint and grant View for GET.
-   **A manager sees every nomination, not only their team’s.** You used a constrained group on page security. Workday says contextual security is not applied to Extend pages. Filter in the endpoint, or stop expecting the page domain to do it.
-   **Sandbox has the new domain a day after you promoted, and Production does not.** The domain is a model component. It deploys on the weekly service update after you promote, and only if you made the Thursday deadline for your region. Activating a policy on Development does not activate it on Production.

## Watch Kiweely Vine build, secure and test an Extend app

![Kiweely Vine's Training Approval Extend app: the manager opens the employee's training request from his Workday tasks](https://kiweely.com/guides/first-workday-extend-app-security-domains/media/vine-extend-app-training-approval-8f3cf9bc75d9.webp)

From the film: the manager opens the employee’s request in his Workday tasks.

From two short messages, Kiweely Vine builds a training approval app in a Workday Development tenant. It sets up the app’s access (Employee As Self and Manager) and the approval’s business process security policy, activates the pending security changes, adds the Manager step to the routing, then tests it as the employees and managers through Start Proxy, privacy checks included. 1 h 51 min from sign-up to the checked result.

[Watch the film (15 min)](https://www.youtube.com/watch?v=hoJV5tq90Ug) · [Start for free](https://kiweely.com/sign-in?intent=signup)

## Frequently asked questions

### Does the security domain file grant access?

No. It defines the domain and whether it can be used for pages or orchestrations. Access is the domain security policy you create in the tenant and then activate.

### Which permission do I check for a form that creates records?

Modify, for the groups that should create or change rows. Workday’s service-domain rule is View for GET and Modify for POST, PUT, PATCH, and DELETE. The nomination tutorial checks Modify for HR Administrator and says that choice affects both the model’s REST security and the pages.

### Can Developer Agent complete this tutorial for me?

It can generate the domain component. The overview says it does not configure security. Steps in App Manager, the security group, and Activate Pending Security Policy Changes stay with you.

### Do I reinstall the app after I change the policy?

No. The policy is tenant configuration. You reinstall only in the refresh cases Workday documents elsewhere. You do promote and wait for Friday when the domain itself is new to Implementation, Sandbox, or Production.

## Sources checked

-   [Add Security Domains](https://developer.workday.com/documentation/azx1677268395516/AddSecurityDomains)
-   [Concept: Extend App Security](https://developer.workday.com/documentation/vel1628698852360/ConceptExtendAppSecurity)
-   [Build an Extend App Fast with Developer Agent](https://developer.workday.com/documentation/GUID-73f17cca-3686-4921-84bf-44b819d9671e-enHYPHENus/BuildanExtendAppFastwithDeveloperAgent)
-   [Concept: Extend App Components](https://developer.workday.com/documentation/kwv1612374098305/ConceptExtendAppComponents)
-   [Developer Agent Overview](https://developer.workday.com/documentation/GUID-f1ddebc6-077a-4441-a023-3c857db88053-enHYPHENus/DeveloperAgentOverview)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Workday Extend Model Components and the Weekly Update Business objects, security domains, attachments, processes, reports, and tasks are model components. Development deploys immediately. Other tenants get model changes on Friday night, and only if you promoted before Thursday. Deployed model components cannot be removed.](https://kiweely.com/guides/workday-extend-model-components-weekly-update)
-   [### The Validate and Deploy Proof Ladder for Workday Extend Preview and validate before a tenant sees anything. Save to App Hub writes a build. Deploy reaches a development tenant only. Promote one level at a time. Model components still wait for the weekly update. Orchestrations validate in Orchestration Builder.](https://kiweely.com/guides/workday-extend-validate-deploy-proof-ladder)
-   [### Promote a Workday Extend App Past Development Deploy and test on a development tenant, then promote only to the next level. Implementation can take a minute to refresh. Sandbox and Production can take 15 minutes. Model components still wait for Friday if you made the Thursday deadline. Install once per tenant.](https://kiweely.com/guides/workday-extend-promote-past-development-beginners)
-   [### Build Your First Workday Extend App with Developer Agent Developer Agent proposes Extend components in App Builder. You still create or accept the business object and security domain, apply the diff, validate, deploy to a development tenant, and activate the domain security policy yourself.](https://kiweely.com/guides/first-workday-extend-app-developer-agent)

### More guides on Extend apps and pages

[All 97 guides](https://kiweely.com/guides#extend)

-   [Is there an AI tool that can build, validate and deploy Workday Extend apps?](https://kiweely.com/guides/ai-tool-build-validate-deploy-workday-extend-apps)
-   [AI Browser Testing for Workday Extend Pages: Grids, Attachments, and BP Steps](https://kiweely.com/guides/ai-browser-testing-workday-extend-grids-attachments-bp)
-   [Workday Extend App Preview Is Not Proof the App Works in the Tenant](https://kiweely.com/guides/workday-extend-app-preview-is-not-tenant-proof)
-   [How to Map Control Fields and Related Business Objects in Workday Composite Subreports](https://kiweely.com/guides/workday-composite-report-control-fields-business-object-swap)
-   [Workday Lookup Related Value (LRV) Explained: Crossing Business Objects Without Blank Rows](https://kiweely.com/guides/workday-lookup-related-value-lrv-calculated-field)
-   [Fixing Graph API DataSourceFilter Is Inaccessible Errors and Blank processingWorker Fields When Proxying](https://kiweely.com/guides/workday-graphql-datasourcefilter-inaccessible-processingworker-proxy)
-   [Clearing Single-Instance Relationships to Null and Binding createdBy with graph:createId() in Graph API](https://kiweely.com/guides/workday-graphql-clear-single-instance-null-graph-createid)
-   [Why Attachment Model Components and contentType Are Missing from the GraphQL Schema After Migrating to IMPL](https://kiweely.com/guides/workday-graphql-attachment-schema-contenttype-missing-impl)

### From the blog on Extend apps and pages

[All posts](https://kiweely.com/blog)

-   [Desktop apps for Extend and Studio](https://kiweely.com/blog/desktop-app-for-workday-extend-and-studio-developers)
-   [Workday Opened Extend to Individual Developers. Here’s What It Changes](https://kiweely.com/blog/workday-opens-extend-to-individual-developers)
-   [Debugging Workday Extend web services: Postman vs. kiweely](https://kiweely.com/blog/debugging-workday-extend-web-services-postman-vs-kiweely)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
