Skip to main content

Hello, 

when a requester requests a service for someone else - and this person (mail address) is not yet a requester (account) - a new requester account gets created automatically. How can I disable this behaviour? 

Our requesters base on Active Directory. If requests can create requesters by themselves our workflows break (those users don’t exist in our AD for example) etc. and we loose control. That is a very big problem. 

Does anybody know how this works?

Greetings

@j.themann there is no way to prevent this, I’ve asked multiple times because it wreaks havoc in our environment. You can auto delete the “fake” requester account using a scheduled workflow automator and some api’s but thats about it.


This is just unbelievable. Today we noticed several requester accounts which have been created this way, and are in theory able to login to our ticketsystem now, access our solutions DB, and so on. I cannot believe there is no way to disable this.


@mhi you can block certain domain’s but that isn’t helpful to an extent.  We literally go through weekly to remove “ghost accounts” and unauthorized accounts.  I truly don’t understand it as well, at least make it to where if you're not using the MSP version of freshservice that you can block requesters being made. There should definitely be an option to click that says allow requesters to be made outside of integrations or something to that affect.