11 Pitfalls to Avoid While Deactivating an Admin in Salesforce | Salesforce Ben

— by

Avoid these common pitfalls when deactivating a Salesforce admin.

1. Admin Reassignment
– Transfer ownership of all records.
– Ensure active users take over admin responsibilities.

2. Scheduled Jobs
– Identify and transfer any scheduled jobs owned by the admin.
– Reassign these tasks to another active user.

3. Delegated Approvers
– Change delegated approvers to prevent workflow disruptions.
– Verify that new approvers are correctly set up.

4. Single Sign-On (SSO)
– Update SSO configurations.
– Ensure no authentication issues post-deactivation.

5. Connected Apps
– Review permissions tied to connected apps.
– Reassign as needed to maintain continuity.

6. Public Groups & Queues
– Reallocate admin from public groups and queues.
– Confirm visibility and access remain unchanged for users.

7. Workflow Rules & Processes
– Audit workflows and processes linked to the admin.
– Redirect any notifications or actions appropriately.

8. Email Alerts
– Update email alerts to reflect active recipients.
– Prevent loss of critical communication.

9. Security Settings
– Revise security roles and permissions.
– Protect sensitive data and maintain access control.

10. Backup
– Perform a data backup before deactivation.
– Safeguard against unintended data loss.

11. Documentation
– Maintain clear documentation of changes made.
– Facilitate smooth transitions and future audits.

Ensure all bases are covered before deactivating an admin to maintain seamless operations and safeguard data integrity.

You can read it here: https://sfdc.blog/hrquw

Source from salesforceben(dot)com

Newsletter

My latest updates in your e-mail.