How do you handle alumni users from a login/password perspective?

[alijubran]

I'm curious on how others are handling the alumni feature so that users no longer need a company email/LDAP login.

An option I'm exploring is taking the personal email address from the HR profile and making it the new userID of their user record and generating a local password much like the new hire does. This way it is still the same user record and we can see all the past cases associated with them when they were an active employee.

The trigger for this would be the employment end date on the HR profile.

Would love to get some other's perspectives.

[Mike Allen]

Instead of deactivating the user or deleting the user, can you not just lock them out when they leave the company?

[alijubran]

Locking them out would prevent them from logging in. I believe the HR product requires the user record be set to inactive and they are granted the alumni role. This would still grant them access to the HR portal. My inquiry is more on how do you manage this person's password/login if they are no longer in AD or can no longer be authenticated through LDAP/SSO?

[Mike Allen]

Each user record has a source and an LDAP server field.   I think that you can make an SSO login (from LDAP) a local login by clearing these fields and setting a password.

[Mrman]

Hi , Could you please let me know what was the solution you found for former employees (aluminis) to be able to access HR portal. We have a similar requirement for alumini to access few knowledge articles and complete certain off boarding tasks .