---
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: >-
Reference: Security Domain Naming Conventions
layout: subsection
---
When you create new security domains for your Workday Extend apps, we recommend that you use the same naming conventions as Workday-delivered security domains.
- Set Up: (Insert Name)
This domain secures setup tasks and corresponding reports.
Examples: Set Up: Benefits, Set Up: Business Entity, Set Up: Jobs and Positions.
- Self-Service: (Insert Name)
This domain secures employee self-service tasks and corresponding reports. These domains can only have Self Groups (Example: Employee as Self) on the policy, which enables users to perform actions for themselves.
Examples: Self-Service: Awards, Self-Service: Personal Information.
- Manage: (Insert Name)
This domain secures tasks, reports, and data that are:
- Cross-company
- Cross-functional
- Cross-worker
Examples: Manage: Candidates, Manage: Cost Center, Manage: Credit Card Data.
- Audit: (Insert Name)
This domain secures tasks and reports related to auditing data.
Examples: Audit: Contact Information, Audit: Worker IDs.
- Reports: (Insert Name)
This domain secures reports and reporting items only. Security policies shouldn't have any groups with modify access or functional dependence on specific roles.
Examples: Reports: Manager Financial Budgets, Reports: My Organization Roles.
- View: (Insert Name)
This domain gives access to view a specific entity.
Examples: View: Customer, View: Supplier.
### Related Information
[Add Security Domains](/wcp_docs/azx1677268395516.html)