The Yandex 360 administrator documentation defines the email archive as a feature that preserves copies of every message sent or received by employees whose mailboxes belong to the organization's domain. Once enabled, the archive continues to retain messages even if the original owner deletes them from their mailbox. The guide explicitly warns that messages deleted before the archive was turned on cannot be restored.
Search functionality is implemented as named objects rather than live queries. The documentation states: “Each search runs once. The results do not update as employees send and receive new messages.” Administrators must either create a new search with identical parameters or use the “Clone search” button and adjust the date range to obtain fresh results. No method exists in the documented Yandex 360 API to automate this process.
The action log records every interaction with the archive and promises that “you can always see who searched for what.” However, the employee filter only lists active accounts. The documentation advises that if an administrator has left the organization, their actions cannot be selected by name in the filter and other criteria such as event type and time period must be used instead.
Additional constraints listed in the FAQ section include the permanent loss of messages belonging to fully deleted accounts and the exclusion of any mail from mailboxes that were imported rather than created on the organization's domain. These documented limitations affect routine tasks such as retrieving correspondence of a departed employee or reconstructing an audit trail after an administrator departure.
