---
category: [Administration & Integrations, Administration & Integrations/Custom Integrations & Apps, Platform and Product Extensions, Platform and Product Extensions/Workday Extend, Platform and Product Extensions/Integration]
keyword: [Extend, Model Components, Model Domains, Security Domain, Extend Domains]
nav: wcp_docs
parent_url: /wcp_docs/
title: Add Security Domains
layout: subsection
---

### Prerequisites

<a id="prereq_rxf_tws_pwb"></a>
[Create Extend Apps Using App Builder](/wcp_docs/xer1651695264256.html)

### Context

<a id="context_it5_x1v_v4b"></a>
Security domains:

-   Extend Workday’s configurable security model to secure app data confidently.
-   Configure security policies in the same manner as the Workday application.
-   Leverage existing security groups and roles to simplify access controls.
-   Can provide page-level security.


### Steps

1.  <a id="step_N10080_N1007D_N10052_N10001"></a>In App Builder, add a <b>Security Domain</b> component.
2.  <a id="step_N10057_N1002E_N1001E_N10001"></a>Author 1 or more security domains for your app. Security domain names must use upper camel case. Example using Code mode:

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

    <b>Note:</b> When you create a security domain, the plugin assigns the default label, `"My Security Domain"`. Workday uses this label to display the security domain in <b>App Manager</b> and related actions. Ensure that you update the default label.

3.  <a id="step_N100AD_N1006C_N1004C_N10001"></a>To secure the pages of your app with a security domain, add the `"enabledForPageSecurity": true` property setting.

    Example:

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

    Only add the `enabledForPageSecurity` property to the security domain if you use the domain for page security.

    <b>Note:</b> Because Workday doesn't apply contextual security to the pages of an app, we recommend that you use only unconstrained role-based security groups for page security. Constrained security on the pages of an app is derived from the endpoint authentication scheme.

4.  <a id="step_1"></a>To secure the orchestrations of your app with a security domain, add the `"enabledForOrchestrationSecurity": true` property setting.

    Example:

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

    Only add the `enabledForOrchestrationSecurity` property to the security domain if you use the domain to secure orchestrations. When enabled, you can apply domain security policies to orchestrations, leveraging Workday's established security mechanisms.



### Related Information

[Concept: Extend App Security](/wcp_docs/vel1628698852360.html)

[Concept: Allowed Security Group Types for Extend Apps](/wcp_docs/nnr1674235989423.html)

[Administrator Guide: Concept: Configurable Security](https://doc.workday.com/admin-guide/en-us/authentication-and-security/configurable-security/configurable-security-basics/dan1370797393969.html)

[Manage Deployed Extend Apps](/wcp_docs/bwl1559331246809.html)

[Steps: Secure the Pages of an Extend App](/wcp_docs/sfv1677268046417.html)

[Reference: Model Component Attributes](/wcp_docs/hod1558556125085.html)

[Reference: Security Domain Naming Conventions](/wcp_docs/yms1650325033219.html)