Skip to main content
darkknight
Expert ⭐️
March 2, 2020
New Idea

Need ability to delete users from User Management

Related products:CS Authentication & User Management
  • March 2, 2020
  • 51 replies
  • 1489 views

I’ve been running into issues where we have users in my environment that have duplicate Usernames but different SFDC User IDs, however when I compare them to their Salesforce counterparts the usernames are different.  I have to assume this is due to some upstream issue - changes made in SF that are out of my control and/or occurred before I came here - but this causes issues for me because the Salesforce Connector user job won’t allow me to use the SFDC UD as an upsert key, so I end up with partial failures related to the duplicate usernames (my upsert key).

When I run into these types of situations my only recourse is contact Gainsight support to delete the user for me.  I need more control over my user table with the ability to delete users.

    51 replies

    cmultanen
    Helper ⭐️
    April 27, 2021

    Is this still on the roadmap? Duplicate users continue to be an issue for our org. 

    soumitrasahu
    Helper ⭐️⭐️
    June 8, 2021

    @cmultanen Yes, this is in the roadmap but we do not have any update on the timelines yet. We will post once we have an update on the timeline.

    Contributor ⭐️⭐️⭐️⭐️⭐️
    July 6, 2021

    Adding my vote to this as we also need to use the SFDC ID as a unique identifier versus the username.

    HollySimmons
    Helper ⭐️
    July 7, 2021

    I’ve stopped syncing SFDC users because of this issue, it means manually adding them when needed, which is a burden but better than having erroneous data loaded that can never be deleted (and by that I don’t mean either option is ideal). 

    mark_deegan
    Contributor ⭐️⭐️⭐️
    July 13, 2021

    any update on this? 

    Seems a pretty common request 

    sagan_sherlin
    Helper ⭐️⭐️
    September 7, 2021

    +Infinity.  Running into this that for whatever reason, a user was duplicated in Gainsight - due to something in SFDC.  Having the ability to clean this would, be amazing!

    Neha Gupta
    Contributor ⭐️⭐️⭐️⭐️⭐️
    September 8, 2021

    Hi @mark_deegan @HollySimmons  @vmoore 

    We are planning to put user delete in our short term roadmap. We will keep you posted.

    Thanks and regards,
    Neha

    Neha Gupta
    Contributor ⭐️⭐️⭐️⭐️⭐️
    September 9, 2021

    Hi  @sagan_sherlin 

    We are planning to put user delete in our short term roadmap. We will keep you posted.

    Thanks and regards,
    Neha

    Contributor ⭐️⭐️
    February 1, 2022

    I’ve been running into issues where we have users in my environment that have duplicate Usernames but different SFDC User IDs, however when I compare them to their Salesforce counterparts the usernames are different.  I have to assume this is due to some upstream issue - changes made in SF that are out of my control and/or occurred before I came here - but this causes issues for me because the Salesforce Connector user job won’t allow me to use the SFDC UD as an upsert key, so I end up with partial failures related to the duplicate usernames (my upsert key).

    When I run into these types of situations my only recourse is contact Gainsight support to delete the user for me.  I need more control over my user table with the ability to delete users.

    @darkknight was Gainsight support able to delete the users for you?  I am being told it is not possible.

    Contributor ⭐️⭐️
    February 1, 2022

    Hi  @sagan_sherlin 

    We are planning to put user delete in our short term roadmap. We will keep you posted.

    Thanks and regards,
    Neha

    @Neha Gupta what does the short term roadmap look like?  I see this was suggested about 4 months ago (Sept/Oct timeframe?).  Would love to understand what the timeline is for this as it is causing problems for me where inactive users are appearing as options to tag individuals in timeline activities and the like.  The only option I am being given is to go in and change all of the deactivated emails to deactivated@XXX.com which doesn't solve the issue… its just a band-aid.