Ways back in help

Choose the archive to manage. The overview shows its ways back in. Create an archive code, test a recovery code, replace a recovery code, optional vault and recovery open on separate pages. Archive codes and keys are handled on your device. Creating a code never overwrites an existing code. The vault requires separate consent and means LexiCo can technically open the archive. Recovery requires email confirmation, a 48-hour wait and custodian approval. Changing archives returns to the overview. The vault is enabled only after you explicitly check I consent for the selected archive. Consent is recorded with its text version and timestamp. If consent is missing when enabling the vault, a message appears in your selected language. Your archive passphrase is kept and the vault is not enabled. Recovery applies only to the selected archive. Normal navigation does not stop the request or waiting period. A device may still open an archive if it has a saved unlocked key; this is not completed vault recovery. Local unlock and cached entries are separated by archive. After a security update, you may need to enter the archive passphrase again. Keep the same browser profile and do not clear browser data while recovery is in progress. Email status indicates whether sending the confirmation code succeeded, failed or is unknown. The request and device key are kept if sending fails. Notification links return to recovery for the specific archive. If an existing request has no device key, use the device and browser profile where it was started. Do not confirm or complete without the key. Contact LexiCo if the key is unavailable there too. Keep browser data and check the status when the outcome is unknown. If the response is lost during completion, the page checks the request ID and saved key envelopes before displaying the new recovery code. If the result is unknown, the proposed result is kept only in this page’s memory; do not reload. A new click checks or continues the same completion without generating new credentials. Starting again while you already have an active request does not replace it or restart the waiting period. Continue on the device where you started the request. Once an unconfirmed email code or the entire request has expired, you can start again. If the email confirmation response is lost, the page checks the status of the same request. If it is already confirmed, the waiting period is preserved without a false error. If the connection is unavailable, the entered email code is kept for retry on the same page. Rapid repeated clicks send only one pending confirmation attempt. An empty email code field displays a message in your selected language without sending a confirmation attempt or consuming a code attempt. Empty fields when testing a recovery code or requesting a new recovery code display a message in your selected language and send nothing. When creating an archive passphrase, the page checks the minimum length and matching fields before creating anything. Code testing and recovery code replacement allow only one pending attempt per page. If the code unlocks the key but saving is unconfirmed, it is not reported as a wrong code. If replacement is unconfirmed, keep the page open and use the same button again. The same proposal is held only in page memory; retry first checks the stored result. A code already displayed remains available if subsequent status loading fails. Ways back in shows separate valuables and travel cards, including archives without a passphrase. Any existing additional archives are preserved. Create a passphrase under the relevant card. Once initialized, its actions open code testing, recovery code replacement, vault and recovery for that specific archive. The card status confirms initialization, not that this device is unlocked. The overview does not change archive selection in other tabs. Before a new vault request is sent, the device key and a fixed request ID are stored together on the device. Storage failure prevents sending. After a lost response, the same startup can be checked or retried, even after reload, in the same profile. The server reuses only the same ID with the same public device key and owner/archive; retry creates no new code or email. Do not clear browser data while the outcome is unknown. After creating an archive passphrase, confirming that you saved the recovery code takes you to the selected archive. Unlock it with your archive passphrase to continue. If you reopen the setup page afterwards, choose “Go to the archive and unlock”. Recovery-code testing and the optional vault remain available later under Ways back in. Once the recovery code is tested and the server has confirmed the record, you automatically return to Ways back in with the same archive selected. The overview shows that the code is tested. An incorrect code or unconfirmed record keeps you on the test page with an explanation.