Deactivating a user should remove them everywhere | Community
Skip to main content
MelissaDa5
MelissaDa5
March 16, 2018
New

Deactivating a user should remove them everywhere

  • March 16, 2018
  • 5 replies
  • 754 views

When a user is deactivated, they should be removed everywhere. I keep finding little easter eggs of old users and can't even begin to find all the places they need to be removed.

Examples, assignments on templates, sharing on projects created from templates, custom views sharing. The only thing that should remain, is a history of what they did. They should not still have views and such shared with them or newly created projects shared/assigned.

    5 replies

    A
    AaronGo2
    May 8, 2018

    Yes!

    T
    TanjaHa
    July 27, 2018

    I fully support that. Specifically, when a profile is deactivated, the system should remove all entries from "Direct Reports" in this profile.

    MoniqueEvans
    Community Advisor
    MoniqueEvansCommunity Advisor
    Community Advisor
    August 6, 2018

    Me and my admins started a dashboard to try to capture all the Easter Eggs of removing a user. To add to this list, you should be prompted just like when you delete an access level that says what User should replace this one. That way any reports that are being run as that person, and pending approvals etc etc are still functional.

    K
    KieranMcK
    December 8, 2020

    Agreed, makes little sense that a user can still be assigned to tasks/projects while deactivated. It should remove all their shares/permissions.

    Jared_Mauch
    Jared_Mauch
    Level 6
    August 20, 2025

    Having to check on the places a deactivated user still has access to and remove them is a big time sync. It would be a huge time saver if deactivated users lost their permissions to items they previously had access to.

    Terms & ConditionsAccessibility statement

    Loading footer...