Search the email archive and save searches
Build a focused archive query, inspect result context, and preserve useful criteria without exposing sensitive search terms.
Audience, roles, and scope
Workplace archive search and saved-search interface; legal conclusions and hold administration require the responsible specialist.
Who this is for
- Users authorized for the email archive
Roles
- Archive user
- Reviewer
Before you begin
- Archive entitlement and authorized scope
- Documented search purpose and relevant date or participant criteria
Article tags
- archive
- email-search
- saved-search
- ediscovery
Procedures
Follow the sequence and stop when identity, authorization, target, or result differs from the article.
Run and save an archive search
Start narrow, validate representative results, then save only necessary criteria.
- 1Define criteria
Use authorized participants, terms, date range, or other visible filters and avoid unnecessary sensitive terms.
- 2Validate results
Inspect result counts and representative messages, checking sender, recipient, timestamp, and scope before relying on them.
- 3Save the search
Give the query a non-sensitive descriptive name, save it if permitted, and reopen it to verify the retained criteria.
The result set reflects the intended authorized criteria and any saved search can be identified safely.
Security and data handling
- Use only the identity, tenant, role, and data scope approved for the task.
- Verify targets and expected effects before saving, sending, publishing, exporting, deleting, or approving.
- Keep secrets and regulated data out of screenshots, URLs, free-text diagnostics, and ordinary support messages.
- Archive access does not authorize disclosure; apply legal, privacy, employment, and investigation controls to results.
Known limitations
- Search completeness depends on indexed sources, retention, ingestion state, permissions, and query semantics.
- Saved searches store criteria, not proof that results remain unchanged over time.
Troubleshooting
You cannot open Vianordis Workplace
Likely cause: The session expired, the account is not entitled, or the required tenant or role claim is missing.
- Open the service through the approved Vianordis entry point and sign in again.
- Confirm the intended organization, tenant, and account are in use.
- If access remains denied, record the time and request an entitlement check; do not attempt direct-URL bypasses.
A documented control or navigation item is not visible
Likely cause: The current role, subscription, tenant configuration, release status, or feature flag does not expose it.
- Confirm the audience, role, prerequisites, and limitations in this article.
- Refresh after a new sign-in and verify the correct tenant context.
- Ask the responsible administrator whether the capability is enabled before reporting a defect.
A saved change or background result is not visible
Likely cause: Validation failed, processing is incomplete, the view is stale, or the feature is locally simulated rather than persisted.
- Review inline validation, status indicators, filters, and the selected tenant or workspace.
- Refresh once and search by a stable identifier before repeating the action.
- Do not repeat irreversible or externally visible actions until the first operation's state is known.
Source verification
Archive query fields, results, detail navigation, and saved-search controls were reviewed in source.
Reviewed paths at 5752ab1
src/app/archive/page.tsxsrc/app/archive/saved/page.tsxsrc/components/archive/ArchiveList.tsxsrc/components/archive/ArchiveSidebar.tsx
Contact support
Contact support when
- A repeatable Vianordis Workplace error blocks an approved task
- Expected access, tenant scope, data, or status appears incorrect
- A security, privacy, financial, compliance, or data-loss concern is suspected
Include
- The page, action, expected result, and exact error text
- The time of occurrence with time zone and whether it is reproducible
- Your tenant, role, browser, and sanitized record or correlation identifier
- The troubleshooting steps already completed
Never include
- Passwords, access tokens, API keys, recovery codes, session cookies, or private keys
- Unredacted personal, financial, health, student, employee, or other regulated data
- Confidential documents or message bodies unless support provides an approved secure channel