ssm.ro Docs
User GuidesUser GuideElectronic Archiving

IronMountain AE Archiving

How to configure and use the IronMountain Archive Engine (AE) archiving module in the ssm.ro admin panel.

The IronMountain AE Archiving module enables the automatic sending of approved documents from the platform to the IronMountain AE electronic archiving service, ensuring compliance with legal archiving requirements.

1. Configuring the connection

From the Connection tab, fill in the details provided by IronMountain:

FieldDescription
ProThe production code / organization identifier provided by IronMountain
TokenThe authentication token for the IronMountain AE API
Request IDThe request identifier provided by IronMountain

Click "Save connection". The system saves the credentials.

Activate the connection using the "Active connection" toggle. On activation, the system automatically verifies that the data is valid and that the connection works.

If activation fails, contact the IronMountain team to verify the credentials.

2. Selecting archived documents

From the Documents tab, check the document types from the employee file that will be automatically archived in IronMountain AE. Automatic archiving runs daily; in addition, each eligible document can also be archived manually.

Unchecked documents are not archived, regardless of the connection status.

3. Tracking archiving

The main tab displays three lists:

TabDescription
ArchivedDocuments successfully sent to IronMountain AE
Not archivedEligible documents that have not yet been sent
IgnoredDocuments excluded from archiving

If the connection is active, automatic archiving happens daily. Documents in the Not archived list (eligible, not yet sent — e.g. those approved before the connection was activated) can also be archived manually at any time.

1. Main interface — tabs

The module's main page is organized into three tabs:

The "Archived" tab

Displays revisions already successfully archived in IronMountain AE.

ColumnDescription
File nameThe title of the archived revision
AE file IDThe document identifier in the IronMountain AE system
Archiving dateThe date and time the archiving was performed

The "Not archived" tab

Displays PDF-type revisions with approved or archived status, configured for archiving, which have at least one associated electronic signature, but have not yet been archived.

ColumnDescription
File nameThe title of the revision
Actions"Archive" button for manual archiving

The "Ignored" tab

Displays records whose document type is not configured for archiving. These documents will not be archived automatically.

2. Configuring the AE connection

The connection to the IronMountain AE server is configured from the "Configure Connection" button.

FieldDescription
PROThe organization identifier (client code) in the IronMountain AE system
TokenThe authentication token for the IronMountain AE API
REQ IDThe request/contract identifier in the AE system

Click "Save" to save the configuration.

3. Activating and deactivating the connection

The "Active connection" toggle controls whether automatic archiving is active.

  • Activation: The system tests the connection to the IronMountain AE API. If the test fails, the connection is not activated and an error message is displayed.
  • Deactivation: Stops automatic archiving. Documents already archived are not affected.

Always verify that the connection details are correct before activation.

4. Configuring archived documents

From the "Configure Documents" button, you can select which document types (RequiredRecords) will be archived automatically in IronMountain AE.

FieldDescription
Active archivingYes/No toggle — whether revisions of this document type are archived automatically

Unlike M-Files, IronMountain AE does not require a document ID per type — mapping is done automatically based on the connection credentials (PRO, Token, REQ ID).

5. Manually archiving a document

From the "Not archived" tab, you can manually archive a revision:

  1. Locate the desired revision in the table
  2. Click the "Archive" button next to it
  3. The system sends the PDF file to IronMountain AE via the API
  4. On success, the revision disappears from the "Not archived" tab and appears in "Archived" with the ID received from AE

Possible errors:

  • The AE connection is not active
  • The PDF file is missing from the revision or has no associated electronic signatures
  • Communication error with the AE API
  • The document has already been archived

6. Viewing the metadata of an archived document

From the "Archived" tab, click on a document to view its metadata from IronMountain AE.

The metadata is retrieved in real time via the API and reflects the current state of the document in the archiving system.

If the connection is inactive or the AE API does not respond, displaying the metadata will fail with an error message.

7. Differences from the M-Files module

AspectIronMountain M-FilesIronMountain AE
PlatformM-Files CloudVaultIronMountain Archive Engine
Connection protocolREST API with session token (username + password + vault GUID)API with PRO + static Token + REQ ID
Archiving conditionApproved/archived PDF revision, configured document typeApproved/archived PDF revision, with electronic signatures, configured document type
Document type mappingRequires an M-Files document ID per document typeNo additional ID required
Connection validationObtaining an authentication tokenConnectivity check call