Access control for Data Mappers and Integration Procedures
Key Takeaway
Set "Required Permission" on an Integration Procedure to a custom permission to limit who can run it. The caller's setting overrides the setting of the Data Mapper it calls, so the same custom permission also controls access to that Data Mapper's data.
Data Mappers and Integration Procedures are Omnistudio components, and you decide which users can run them. You can secure them as records with sharing and permissions, or you can list who may run each one in its Required Permission property. Org-wide security settings in "Omni Interaction Configuration" add more checks, such as field-level security and Apex class access.
Ways to control access
Sharing Settings, Sharing Sets, profiles, and permission sets control access to Data Mappers and Integration Procedures as object records.
You can secure these components with Sharing Settings, or you can allow access based on the custom permissions enabled in a user's profiles or permission sets.
Access is about more than running a component directly: it also applies when an application the user is working in calls the Data Mapper or Integration Procedure.
In all Salesforce orgs, guest users, also called anonymous users, cannot access any records by default. Criteria-based Sharing Rules give guest users read-only access, and no other configuration is needed for that access.