Skip to main content
Solved

Unable to deactivate users in sandbox!

  • January 16, 2026
  • 7 replies
  • 70 views

Forum|alt.badge.img+1

Hi! I’m unable to deactivate users/requesters in my sandbox environment. It works fine in prod though. Is this a limitation or is it something that I can turn OFF from my side?

Best answer by Nav_in

Hey ​@Optimus_prime ! Currently in FS, requesters and agents cannot be deactivated in the sandbox (manually or via API). This seems to be a security measure in place because, in some cases, deleting a requester or agent in the sandbox can also trigger deletion in the development account during synchronization. Hope this helps!

7 replies

Forum|alt.badge.img+7
  • Top Contributor ⭐
  • Answer
  • January 19, 2026

Hey ​@Optimus_prime ! Currently in FS, requesters and agents cannot be deactivated in the sandbox (manually or via API). This seems to be a security measure in place because, in some cases, deleting a requester or agent in the sandbox can also trigger deletion in the development account during synchronization. Hope this helps!


Forum|alt.badge.img+10
  • Skilled Expert
  • January 20, 2026

Limitation it appears. You cannot deactivate someone in a sandbox only. Only way to, is disable them in prod too. 

 

You can weirdly create them an account in dev only but you cannot remove it / deactivate it. Which is frustrating. Unsure why you can create but not deactivate a user. 


i am facing same issue


Forum|alt.badge.img+1
  • Author
  • Apprentice
  • January 21, 2026

Thank you ​@Nav_in !! You are totally right ​@Cara !! Not sure why this limitation exists! We want to deactivate and reactivate users in sandbox for testing purposes, but if we can only achieve the same by deactivating them in prod environment, I’m not sure how testing can be done in the first place!


Forum|alt.badge.img+10
  • Skilled Expert
  • January 22, 2026

We don’t normally give everyone access to dev. Only when they need it so the benefit of being able to activate and deactivate users in dev is quite a bit. Plus we don’t want the risk of them accidentally logging tickets in the dev environment instead of the prod. This has happened before and teams were processing tickets that were meant only for testing purposes. 

 

We only want to be able to give dev access when we need it for testing and sometimes there are times when we have people that we do not yet want to be agents in prod because they are still deciding if they want to have access to the system so we only want to give them dev access and then remove it later if they decide they don’t want to be but with the system currently, it is not something we can do or want to do. 


chickpeafilae
Apprentice
Forum|alt.badge.img

Facing the same issue. Please help.


Forum|alt.badge.img+10
  • Skilled Expert
  • January 28, 2026

Facing the same issue. Please help.

Unfortunately, we can’t. It needs to be changed by Freshworks, otherwise it is working as intended. Which is not what we want.