A user returns from extended leave

You can use this checklist to reverse the actions you completed using the User Takes Extended Leave checklist when a user returns from an extended leave. See A user on extended leave

Note: The system administrator and users with the appropriate role can access these features. See What are Roles and Secured Actions?

This checklist uses the same scenarios. However, this time, you can complete the All Scenarios items first, and then continue with any additional items for the appropriate scenario that fits your organization.

All Scenarios

If you prevented the user who took leave from logging on during his or her absence, access the User detail view and select the Login Enabled check box.

Scenario A

Teams own accounts and both users taking a leave and the replacement user are in the same team(s).

No special steps are necessary for this scenario. The user who took leave must continue to have access to the same accounts as the replacement user since they are on the same team.

Scenario B

Teams own accounts, however, the user taking leave and the replacement user are not in the same team(s).

Referring to your notes from when you added the replacement user to the necessary team(s), remove the replacement user from the appropriate team(s). See Removing a team member

Scenario C

Individual users own accounts.

You can access User detail view for the user who took leave.
You can click User Team Members tab and click Remove hyperlink for the replacement user. See User Team Members Tab
Removing this person from the profile prevents them from continuing to access the accounts owned by the user who took leave.

Scenario D

Your organization uses the system group Everyone for account ownership.

No special steps are necessary for this scenario. The user who took leave should continue to have access to all accounts since your company uses the system group Everyone for account ownership.