An administrator at Cloud Kicks is designing an enterprise access control architecture using Permission Sets and Permission Set Groups. Match each specific administrative requirement on the left with the correct Salesforce configuration mechanism on the right.
- Granting temporary access to manage sensitive financial fields for a 14-day audit project without modifying baseline profile settings.Permission Set Expiration Date Assignment
- Restricting 'Delete' access on the Account object for users assigned a bundled set of permissions, without modifying the underlying component permission sets.Muting Permission Set
- Combining multiple distinct permission sets ('Lead Manager', 'Opportunity Approver', and 'Contract Editor') into a single reusable package for simplified user assignment.Permission Set Group
- Providing additive 'Read' and 'Create' permissions on a custom 'Audit Log' object to a select group of users spanning multiple departments.Standalone Permission Set
Answer
The correct matches pair temporary financial field access with Permission Set Expiration Date Assignment, restricting delete access within a bundle with a Muting Permission Set, combining permission sets into a single package with a Permission Set Group, and extending custom object permissions with a Standalone Permission Set.
Each administrative requirement aligns with a specific Salesforce security feature: temporary access requires assignment expiration dates; masking permissions within an aggregated bundle requires a muting permission set; packaging multiple permission sets together requires a permission set group; and granting incremental permissions across different roles requires a standalone permission set.
Step-by-Step Solution
Key Concept
Permission Sets, Permission Set Groups, Muting Permission Sets, and User Assignment Expiration
Estimated Time:2m 0s