For organizations that may be unable to use the built-in Apricot archive yet, it would be nice to have some more granular settings to control when/how the archive option is provided on end user communications and allow us to integrate our own archive processes, so we can still use Apricot as much as possible. For example, ability to toggle presentation of the archive option to end users on/off (preferably independent of whether storage is setup or not) , option to configure Apricot to either Archive using Apricot native mechanism or an external mechanism, ability to provide a URL where the Archive button on inactive emails should redirect end users if external archive is configured. This would allow us to send them to a page to give them additional guidance on archiving, collect additional info and/or give them way to request archive (ticketing system). For example, we may need to know how long the data needs to be retained. If Apricot could still keep track of the fact that the end user has decided the site should be archived, even if we are not using Apricot native archive, that would be helpful so we could see a list of sites that need to be archived outside of Apricot.