I have a User, Who will leave the organization tomorrow. He is basically a manager and there are 15 users below him. Now when this user leaves the organization I would generally inactivate the User. But now my concern is if I inactivate this user What happens to the Role hierarchy? the assignment rules, Approval processes, the records created by him and records to which he is the default owner like leads and cases. what would be best possible solution to keep this application intact and running and yet have this user deactivated?
Approval process will remain active. however if this user who you are going to deactivate is the only approver, other users will not be able to submit record for approval, it will say there is no active approval process..Role hierarchy will remain as it is so will be sharing rules.Records created by him will remain as it is.wherever he is default owner, those things will also remain as it is. this is y it is important to have a de-boarding process...
a sample de-boarding process could be something like this - whenever someone leaves, assign all of its record to its manager. if user you are going to deactivate is manager of few users, roll that thing to current user's manager. few of the things u might need to check manually, like default lead owner, or reports saved on his personal folder, and dashboard associated etc. however no user should be directly assigned to assignment rule or any other process automation rule.. try to do that via queue for ownership and public group for visibility.
See.. React is totally a front end where as salesforce has both front end and backend.. it depends on what u like more.. both are good.. U can even do both if u have genuine interest on Front end.
Simple and yet very informative video ❤️
Thanks Revanth , glad u liked it.
Please make more videos on admin related topics
Thank you ❤❤ keep posting Sir love your content❤❤
Keep watching bro
Great content bro
Do make more videos on Admin interview Topics .
Sure
Very informative!
Glad you think so!
Nice video
Thanks Mahesh :)
How many users can be active in a org at a time? Is there any limit?
I have a User, Who will leave the organization tomorrow. He is basically a manager and there are 15 users below him.
Now when this user leaves the organization I would generally inactivate the User.
But now my concern is if I inactivate this user What happens to the Role hierarchy? the assignment rules, Approval processes, the records created by him and records to which he is the default owner like leads and cases.
what would be best possible solution to keep this application intact and running and yet have this user deactivated?
This is important question please tell me the answer..
Approval process will remain active. however if this user who you are going to deactivate is the only approver, other users will not be able to submit record for approval, it will say there is no active approval process..Role hierarchy will remain as it is so will be sharing rules.Records created by him will remain as it is.wherever he is default owner, those things will also remain as it is. this is y it is important to have a de-boarding process...
a sample de-boarding process could be something like this - whenever someone leaves, assign all of its record to its manager. if user you are going to deactivate is manager of few users, roll that thing to current user's manager. few of the things u might need to check manually, like default lead owner, or reports saved on his personal folder, and dashboard associated etc. however no user should be directly assigned to assignment rule or any other process automation rule.. try to do that via queue for ownership and public group for visibility.
@@Mtripathi347 thank you sir
Hello ! I'm confused between react js and Salesforce dev, what should I go for ?: Please let me know
Salesforce
@@ayushsrivastav834 why ?
See.. React is totally a front end where as salesforce has both front end and backend.. it depends on what u like more.. both are good.. U can even do both if u have genuine interest on Front end.