Skip to main content

Sometimes we have break ups


dklinger
Hero III
Forum|alt.badge.img+8

Being rather new with the system - I wanted to see if folks had a feel for a strong order of operations when it comes to how to work through a corporate breakup 😐.

Dont worry - I am not hard deleting anything anywhere….but if I had to think of an order of operations and from a systems perspective?

I am attacking (after understanding what TSAs are in place or not in place):

  1. learning visibility (in the form of courses, training materials, catalogs).
  2. page and menu access
  3. disable integrations that will generate/terminate users
  4. disable user access
  5. send a user report with a smiley face on it

For those that have lived through this before - especially in the Extended Enterprise...any thoughts on - did I pretty much cover it?

Did this post help you find an answer to your question?

7 replies

Annarose.Peterson
Hero III
Forum|alt.badge.img+6

You know what I did in the past, move all the accounts from a deactivated client into a special Deactivated branch. (Each client had their own sub-branch, so we would just move the sub branch folder under the deactivated branch).

Nothing anything was assigned to that deactivated branch, so once we moved the sub-branch over, they immediately lost visibility to everything in one swoop. 


dklinger
Hero III
Forum|alt.badge.img+8
  • Author
  • Hero III
  • 1671 replies
  • May 5, 2022
Annarose.Peterson wrote:

You know what I did in the past, move all the accounts from a deactivated client into a special Deactivated branch. (Each client had their own sub-branch, so we would just move the sub branch folder under the deactivated branch).

Nothing anything was assigned to that deactivated branch, so once we moved the sub-branch over, they immediately lost visibility to everything in one swoop. 

That is a crazy powerful approach @Annarose.Peterson - what a great idea.

I have been working with a branch that has nothing assigned to it when it comes to disabled accounts and accounts that should be removed by audit.


lrnlab
Hero III
Forum|alt.badge.img+8
  • Hero III
  • 4791 replies
  • May 5, 2022

Same as @Annarose.Peterson mentions...it’s the most direct and definitive way to do this. Just make sure to pull your reports before you makes such a move fro archiving...


steveninfinger
Helper III
Forum|alt.badge.img+7

I think we have a slightly different overall EXE use case, but close enough to have a similar requirement. When we have a customer organization leave their branch is moved to an Inactive branch similar to what everyone else is saying, so 3 votes for a working solution that might work for you also.

 


Bfarkas
Hero III
Forum|alt.badge.img+5
  • Hero III
  • 3582 replies
  • May 5, 2022
lrnlab wrote:

Same as @Annarose.Peterson mentions...it’s the most direct and definitive way to do this. Just make sure to pull your reports before you makes such a move fro archiving...

This this and this! When it doubt pull more reports/data for backups.


gstager
Hero III
Forum|alt.badge.img+7
  • Hero III
  • 891 replies
  • May 5, 2022

Something I learned many years ago…

“Save early. - Save often.”

Still good advice.


Bfarkas
Hero III
Forum|alt.badge.img+5
  • Hero III
  • 3582 replies
  • May 5, 2022
gstager wrote:

Something I learned many years ago…

“Save early. - Save often.”

Still good advice.

I have a cubicle neighbor who stares angrily at the “auto save” cloud icon in his office programs now a days and mumbles “I don’t believe you”


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings