Hi Gerald 

As a standard setup of Evolution it's not possible to prevent the second logon from occurring 

However, you can of course have a 3rd party trigger/store procedure developed (by your own identified vendor that is technically qualified) that can control your agents' logon activity. This means, such a custom built trigger/stored procedure should prevent the second logon.

Kind Regards

Bennie 

Hi Gerald 

As a standard setup of Evolution it's not possible to prevent the second logon from occurring 

However, you can of course have a 3rd party trigger/store procedure developed (by your own identified vendor that is technically qualified) that can control your agents' logon activity. This means, such a custom built trigger/stored procedure should prevent the second logon.

Kind Regards

Bennie 

Hi Bennie,

Thank you for your response, I did a trigger already just thought there might be other ways because the client isnt really a fan of triggers.

My pleasure, Gerald