Expired Applications
- 1 Minute to read
- Print
- PDF
Expired Applications
- 1 Minute to read
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
For security and compliance reasons, your institution may want to have applications automatically update to “Expired” status. The automatic expiration is configured in the Admin Platform under Institution Settings and is based on the number of days since the application was last updated and/or the application status.
Note: You cannot change the status of an application once it has expired. To continue applying, the applicant must start a new application.
The following institution settings control expired applications (all three settings are required for the expiration functionality):
- Applications Expire – If set to
True
, this enables the automatic expiration functionality; the default isFalse
(not enabled) - Days to Expire Applications – Once Applications Expire is set to
True
, applications automatically expire if the application has not been updated after the number of days specified here. The default is30
, meaning if there are no updates to the application in 30 days, it will automatically expire. - States to Expire Applications – Once Applications Expire is set to
True
, the automatic expiration only applies to applications that are in the statuses listed here. The default is["creating", "creating_preapproved", "creating_unverified_already_exists_on_core", "creating_verified_already_exists_on_core", "funding_failed", "documents_requested"]
, meaning automatic expiration only applies to applications with the following statuses after the number of days specified above: Creating, Creating Preapproved, Creating Unverified Already Exists on Core, Creating Verified Already Exists on Core, Funding Failed, and Documents Requested.
Was this article helpful?