Including Data for Deactivated Users | Community
Skip to main content
A
AneesahCampbell1
New Participant
December 12, 2022
Solved

Including Data for Deactivated Users

  • December 12, 2022
  • 1 reply
  • 1030 views

We've been in the system for 2 years which means we can finally pull year-over-year data. What I've realized is the data from users that have been deactivated is not included. Does anyone have a solution on how to ensure that data from deactivated users is included in YOY data? I currently have had to reactivate the users to ensure that their data was included. Has anyone had this same experience?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by AneesahCampbell1

Wanted to pull in number of projects owned by deactivated users on a project report. What I've done so far is reactivated with a reviewer license and added to a "Deactivated User Team" to be able to pull in the retroactive metrics. If anyone has any other suggestions, please let me know. TIA.

1 reply

KellieGardner
KellieGardner
New Participant
December 14, 2022

what kind of data are you trying to include? Are you running a specific type of report?

A
AneesahCampbell1AuthorAccepted solution
New Participant
December 29, 2022

Wanted to pull in number of projects owned by deactivated users on a project report. What I've done so far is reactivated with a reviewer license and added to a "Deactivated User Team" to be able to pull in the retroactive metrics. If anyone has any other suggestions, please let me know. TIA.

    L
    LizMiller-BJC
    New Participant
    January 5, 2023

    We have an access level that is called "Deactivated User" and it equates with "Reviewer" so that we can distinguish between actual reviewers and former team members. We leave them on their teams and groups so their work will appear on the appropriate reports. 

    For security reasons, we change their email address/username to a dummy address on their last day so they can no longer access the account and so others will receive a bounce-back if they attempt to message them directly. However, this does create a scenario in which someone may be tagging them in updates not realizing that no one will see them. 

    At this point, we haven't created a process for actually deactivating their account because the data from the past is still relevant for us. That's on my "rainy day to-do list" to figure out, so if anyone has any additional ideas, they would be much appreciated!

    Terms & ConditionsAccessibility statement

    Loading footer...