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

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