---
schema_version: "1"
id: 8ab9913cafce3a9abaf8046dc8b9f1086d40c1e275acdb79c434abeefa2a7157
title: Syntax of the Required Permission Property
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_syntax_of_the_required_permission_property_48272.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_syntax_of_the_required_permission_property_48272.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 0924069d819d32686259eb53ada49774df48766e0aac392bc704a8465f5a1a06
description: Omnistudio Data Mappers and Integration Procedures have a Required Permission property, which determines who has runtime access. You can specify roles, profiles, permission sets, custom permissions, or any combination. If Required Permission is blank, any user can run the Data Mapper or Integration Procedure unless the DefaultRequiredPermission property is set.
products:
  - Omnistudio
release: "264"
---
# Syntax of the Required Permission Property

Omnistudio Data Mappers and Integration Procedures have a Required Permission property, which determines who has runtime access. You can specify roles, profiles, permission sets, custom permissions, or any combination. If Required Permission is blank, any user can run the Data Mapper or Integration Procedure unless the DefaultRequiredPermission property is set.

When an Integration Procedure calls a Data Mapper or another Integration Procedure, the Required Permission setting of the calling Integration Procedure takes precedence. It overrides the Required Permission setting of the called Data Mapper or Integration Procedure.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio-264-0-0-production-enus/f526eaa8-ae05-487a-8944-4bb99b0b78ac/images/icon_note.png)

Note

In Winter '22 and earlier releases of Omnistudio, you can only specify a comma-separated list of custom permission names. For backward compatibility, this simpler syntax is still supported if you only need to specify custom permissions.

The syntax of the Required Permission property is:

```
prefix:name,prefix:name, ...
```

The prefix can be `Role`, `Profile`, `PermSet`, or `CustomPerm`. The name is the name of a role, profile, permission set or permission set group, or custom permission. For example, here’s a Required Permission value that includes two roles and one permission set group:

```
Role:Architect,Role:Developer,PermSet:OmniStudio Admin Group
```