# What is Namirial Archive

**Namirial Archive** is Namirial's document and content platform. It brings
together several capabilities in a single system:

- **Enterprise Content Management (ECM)** — organize and govern business content.
- **Document Management System (DMS)** — store, classify, and retrieve documents.
- **Long-Term Archiving (LTA)** — preserve documents and evidence over time with
digital-preservation guarantees.
- **Business Process Management (BPM)** — model and run document workflows.
- **eDelivery / eInvoicing** — exchange and process electronic deliveries and
invoices.


For Namirial Notify, the capability that matters most is **long-term archiving**.
When LTA storage is enabled for a site, the certified evidence and documents
generated by Notify services are preserved in the customer's Namirial Archive
company, so they remain available and verifiable well beyond the online
retention period.

In the Namirial Notify configuration screens, long-term archive storage is
labelled **LTA Storage** and is provided by **Namirial Archive**. See
[Archiving and retention](/products/namirialnotify/user-guides/archiving) for how retention and custody defaults are configured.

## The Namirial Archive LTA plugin

The connection between Namirial Notify and Namirial Archive is delivered through
the **Namirial Archive LTA plugin**. The plugin links a Namirial Notify site to
the customer's **company** in Namirial Archive and uses the **document type** or
types configured for the Notify integration, so that certified evidence can flow
into long-term custody after transactions close (see
[how archiving happens](#how-namirial-notify-uses-namirial-archive) below).

Activating the plugin is a one-time provisioning task carried out by Namirial
Operations and LTA Support — it is not something an end user sets up. Once it is
active, the per-service **LTA storage** option becomes available in Namirial
Notify.

## How Namirial Notify uses Namirial Archive

With the plugin active, Namirial Notify archives evidence through a per-service
**LTA storage** option. When it is enabled for a service (EviMail, EviSMS,
EviNotice, EviSign, or EviPost), the evidence produced by that service is
archived in Namirial Archive in addition to being kept online.

After the transaction reaches its **closed, final state**, Namirial Notify runs
its post-close archiving steps. When LTA storage is enabled, those steps store a
transaction bundle in Namirial Archive. This happens after tracking closes, not
at submission time and not when the online retention period expires. The online
copy remains governed by its configured retention period. The bundle typically
contains the main document or content, its affidavits, any attachments, and the
recorded notifications or delivery receipts.

The archived bundle is stored under the customer's **company** in Namirial
Archive and classified according to the configured **document type** mapping.
Depending on the tenant configuration, services can use separate document types
or be distinguished by metadata within a shared type. Whether a given
transaction is archived follows the site and user **LTA storage** defaults
described in [Archiving and retention](/products/namirialnotify/user-guides/archiving); API integrators can also
set it per transaction with the optional `LtaStorage` submit option (see the
[API reference](/products/namirialnotify/apis/overview)).

Each successful LTA storage operation is recorded on the transaction itself:
once the evidence has been stored, a **Namirial LTA Stored** event appears in the
transaction's event history. The transaction reaches `Closed` before this
post-close step runs, so `Closed` alone is not confirmation that LTA storage has
finished. Use the **Namirial LTA Stored** history event as the per-transaction
confirmation that the evidence reached long-term custody. This is a transaction
history event, not a `PushNotificationFilter` callback value.

Once archiving is active, users work with the preserved documents directly in
the Namirial Archive platform — searching, organizing, downloading, and
generating preservation packages. The [Using Namirial Archive](/products/namirialnotify/user-guides/using-namirial-archive)
guide walks through those day-to-day tasks.

## Key concepts

Understanding a few terms makes the platform easier to navigate:

| Term | What it means |
|  --- | --- |
| **Company** | The organization instance in Namirial Archive under which documents and evidence are stored. |
| **Document type** | The classification applied to a document. The mapping and available types depend on the customer's Archive configuration; service metadata can further distinguish Notify evidence within a shared type. |
| **Booklet** | A logical folder used to organize archived documents. Booklets are a logical structure only — they do not move the physical file. |
| **MegaSearch** | The main workspace for uploading, organizing, and searching archived documents. |
| **PdD (Distribution Package)** | A downloadable package generated for a document, used to distribute or hand over its preserved content. |
| **Address book** | A managed set of accounts and contacts that can be shared with authorized companies. |


## Who accesses Namirial Archive

Namirial Archive is a separate platform from the Namirial Notify portal, with its
own sign-in. Access is granted to users who need to work with archived documents —
for example, to retrieve preserved evidence, search across document types, or
produce a distribution package for a specific record.

The Namirial Archive interface is a distinct product from the Namirial Notify
portal. Availability depends on the customer's contracted services and enabled
modules.

## Related

- [Using Namirial Archive](/products/namirialnotify/user-guides/using-namirial-archive) — the day-to-day user guide for the platform.
- [Archiving and retention](/products/namirialnotify/user-guides/archiving) — retention, custody, and LTA storage defaults in Namirial Notify.
- [Evidence and affidavits](/products/namirialnotify/user-guides/evidences-affidavits) — what Namirial Notify records and preserves.