A biopharmaceutical company has 150 Clinical Research Associates assigned to a single baseline profile named 'Clinical CRA'. Due to new compliance requirements, a subset of 12 Clinical Research Associates requires temporary Edit access to a custom object named 'Audit Log' for 90 days, while the remaining 138 users must maintain their existing access level. Which solution should the administrator implement to grant this access while maintaining security best practices?
- Create a permission set granting Read and Edit access on the Audit Log object, configure an assignment expiration date of 90 days, and assign it to the 12 Clinical Research Associates.Answer
- BClone the baseline 'Clinical CRA' profile, grant Read and Edit access on the Audit Log object in the cloned profile, and reassign the 12 Clinical Research Associates to the new profile.
- CModify the baseline 'Clinical CRA' profile to grant Read and Edit access on the Audit Log object, then create a validation rule to block access for the remaining 138 users.
- DCreate a standalone Muting Permission Set that revokes Edit access on the Audit Log object and assign it directly to the 138 users who do not need access.
Answer
Create a permission set granting Read and Edit access on the Audit Log object, configure an assignment expiration date of 90 days, and assign it to the 12 Clinical Research Associates.
Permission sets are designed to extend functional access to specific users without modifying baseline profile settings. Using User Assignment Expiration allows administrators to specify an expiration period (such as 90 days), after which access automatically expires.
Step-by-Step Solution
Key Concept
Additive permissions via Permission Sets and temporary access using User Assignment Expiration