Permission Sets for Retail Execution Users

Consumer Goods Cloud primarily uses managed permission sets as the standard for all users. These permission sets are mandatory and essential for automatic push upgrades, ensuring seamless access after updates. All customers, including those on pre-Summer ’24 versions, must use or migrate to these managed sets. The unmanaged permission sets are listed for historical reference only.

You can assign predefined permission sets to different Retail Execution users:

• Administrators: To set up master data objects and maintain retail execution (Field Sales Execution and Field Sales management apps).
• Users: To perform their roles and responsibilities within the org based on user type access. For example, sales reps or supervisors.
• Worker processes: To grant batch users access to run a Consumer Goods Cloud Processing Services worker process.
• Analytics User: To access and analyze Consumer Goods Cloud data.

• Considerations
  Review these important considerations for setting up permission sets.
• Permission Sets From Summer ’24
  Review the recommended managed package permission sets for different user roles within the Consumer Goods Cloud.
• Permission Sets Before Summer ’24
  Before Consumer Goods Summer ’24, permission sets were delivered as static resources (unmanaged permission sets) that customers had to add manually. To avail automatic managed package push upgrades, upgrade to Winter ’26 or higher. Migrate to managed permission sets and reapply your customizations to the new permission sets.
• Assign Permission Sets to Managed Package Users
  Give users access to specific features and functions without altering the existing profiles of the users.
• Review Custom Permission User Role Mappings
  With custom permission user role mapping, users can access the required features or processes they need for their role on the Consumer Goods Cloud mobile app. When you install the Consumer Goods Cloud managed package, the user role mapping is done automatically for custom permissions if you run the PostInstallDemoSetupDataBatch Apex class. If you're a customer who's upgrading the managed package, the user role mapping is done when you manually upload the demo data through Static Resource files for the release.