Can I recover an organization or user if it was accidentally deleted?

Return to top

6 Comments

  • John DiGregorio

    Niall Colferis there a way to remove the deleted organizations from showing up in explorer? I use a report to export data and we have 500+ deleted accounts from our initial seeding that I would like to remove.

    0
  • Dave Dyson
    Hi John, not sure if this would be scalable for your use case, but there's a workaround mentioned here:Zendesk Explore | Removing Deleted Organisations From Filters
    0
  • Michael McMeekin

    I did accidentally find a workaround to recover a permanently deleted user as a self-serve option.

    • Create a new user profile using their name but a tertiary email.
    • Merge the deleted profile with the new profile.
    • The old email information will be added as additional emails, choose the original email and make it primary
    • Now delete the tertiary email from the list of additional emails.
    -1
  • Dave Tonks

    Michael McMeekinHow can you merge a delete profile, it's non-accessible via the front end?

    0
  • Michael McMeekin

    I haven't tried again since I posted the comment in May, at that time, I was able to merge it simply by following the steps described. That said, with the recent security update our users now have external IDs as well, we were going through that transition at the time of the discovery. Looking to attempt a merge now returns an error:

    "You cannot merge "User Name" while they have an external ID.
    Please close this window and try again.

    However, while on the Customer screen, you can:

    • select "Add Customer" (making sure the name matches the deleted profile).
    • You will only add name and email
    • once that customer is created, open that profile
    • select the dropdown and select Merge into another user
    • 被删除的用户将填充mer作为一个选项ge.

    At least that is the way it is working for me.

    Michael

    0
  • Dave Tonks

    Hi Michael, Thankyou for taking the time to reply, I really appreciate it. From my end it looks like they have plugged that particular workaround. Thanks anyway

    0

Pleasesign into leave a comment.

Powered by Zendesk