...

User-Friendly Account Reactivation through Reactivation Policy Options

...

As a security measure, InfraLink User Accounts are automatically deactivated after a period of inactivity. The length of that inactivity period is defined by the instance administrator, but most instances utilize the default setting of 35 days. User Accounts may also be manually disabled by an administrator for a variety of reasons, such as a User no longer supporting a project.

Historically, to regain access to an instance, the User had to contact the instance administrator or Helpdesk to request account reactivation. With Users working a variety of shifts across a number of time zones, this process could sometimes experience delay.

Reactivation Policy per Authentication Provider

To improve the User experience, InfraLink now offers two new features supporting the the timely reactivation of User Accounts:

...

an Account Reactivation Upon Successful Authentication setting, configurable per each Authentication Provider. This setting will be set to one of the following values:

• Reactivate - Upon successful authentication, InfraLink will automatically reactivate

...

• an Inactive account. 
• Request Reactivation (default) - Upon successful authentication, InfraLink transitions the Account to the Reactivation Request status and notifies administrators of the same.

To effectively apply the reactivation policies, InfraLink now differentiates between Automatically Deactivated and Administratively Disabled accounts. Specifically, the User Account status will be set to "Inactive" after the instance-defined period of inactivity, and the User account

To effectively apply the account reactivation policy, InfraLink will differentiate between Automatically Deactivated and Administratively Disabled accounts. Specifically, 

...

status will be set to "

...

Disabled"

...

when the account is manually disabled by an administrator.

...

Reactivate policy Impacts:

• For User Accounts Automatically Deactivated due to inactivity, InfraLink will automatically reactivate the account upon the User's successful authentication. 
• For User Accounts Administratively Disabled, a User's attempted login will trigger an email to instance administrators, advising of the reactivation request. With this scenario, an administrator must log in to the instance and manually approve or deny the request.

Request Reactivation Policy Impacts:

• For User Accounts Automatically Deactivated, a User's attempted login will trigger an email to instance administrators, advising of the reactivation request. With this scenario, an administrator must log in to the instance and manually approve or deny the request.
• For User Accounts Administratively Disabled, a User's attempted login will trigger an email to instance administrators, advising of the reactivation request. With this scenario, an administrator must log in to the instance and manually approve or deny the request.

...

What You Will See in the User Interface:

...