As the world moves to being more connected and allowing collaboration between organizations why can't we have Expiration Dates for User Lists and Users. This would allow better management of 3rd party and temporary access.
I believe that if you go to the user Properties for the specific user in PW Admin, then go to the Settings Tab > General > Credential Expiration Policy, you can set this by Server Default (not sure HOW that gets set), or by "Custom Value". Custom Value only allows up to 999 Hours (roughly 41 days) before expiration. At the very least, it would be beneficial to allow 9999 hours, which is roughly 416 days. This would allow a setting of 8760 (365 days) of flexibility for individual user settings.
Fully supporting this request, in a join venture we have users that leave project but still have a valid email and we want to control Who can access, What they can access and also When they can access.
Along that request above, a user that do not connect for x period of time, should have is access block on a project and he would need to send an email to a specific Email address to re-estate his access and rights to the project
I believe that if you go to the user Properties for the specific user in PW Admin, then go to the Settings Tab > General > Credential Expiration Policy, you can set this by Server Default (not sure HOW that gets set), or by "Custom Value". Custom Value only allows up to 999 Hours (roughly 41 days) before expiration. At the very least, it would be beneficial to allow 9999 hours, which is roughly 416 days. This would allow a setting of 8760 (365 days) of flexibility for individual user settings.
Fully supporting this request, in a join venture we have users that leave project but still have a valid email and we want to control Who can access, What they can access and also When they can access.
Along that request above, a user that do not connect for x period of time, should have is access block on a project and he would need to send an email to a specific Email address to re-estate his access and rights to the project