Thank you Sysadmins! Show some love, join a contest, and win $100 USD, you deserve it all. Win $100 USD

Start a new topic

Best practice for requesters that are no longer company employee's

I've been somewhat frustrated that the AD integration does not "deprovision" requesters when they are removed from AD. I was about to start purging them manually and it occurred to me that some platforms (ex Salesforce) require that account to remain for audit trail purposes and allow you to deactivate and hide the record from view.


What is everyone's practice for dealing with former employee requesters? Do you purge them or something else?


What is the official Freshservice position on this? Will removing requesters have an adverse affect on any product functionality?


12 people have this question

Moreover, you are capable to have an entire picture of what you require now and shortly to retain your customers. SAP Business One gives you the capability to identify, plan and execute actions to align perfect demand and supply balance and thus optimizing your business profits.

Any update on the SCIM implementation?

Hello,


Any updates on supporting Azure SCIM provisioning?


Thanks,

Ilya

Hello!


We already have SCIM apps available for two identity management platforms:


Okta: https://www.freshworks.com/apps/freshservice/okta_provisioning_scim/

OneLogin: https://www.freshworks.com/apps/freshservice/onelogin_provisioning_scim


A similar app for Azure AD has been developed and submitted to Microsoft for approval. We expect the approval to come through in a few weeks.


Mithun Mohandas

Product Manager, Freshservice


2 people like this
Any news? “A few weeks” have passed :)
Login or Signup to post a comment