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:
| Field | Description |
|---|---|
| Pro | The production code / organization identifier provided by IronMountain |
| Token | The authentication token for the IronMountain AE API |
| Request ID | The 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:
| Tab | Description |
|---|---|
| Archived | Documents successfully sent to IronMountain AE |
| Not archived | Eligible documents that have not yet been sent |
| Ignored | Documents 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.
| Column | Description |
|---|---|
| File name | The title of the archived revision |
| AE file ID | The document identifier in the IronMountain AE system |
| Archiving date | The 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.
| Column | Description |
|---|---|
| File name | The 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.
| Field | Description |
|---|---|
| PRO | The organization identifier (client code) in the IronMountain AE system |
| Token | The authentication token for the IronMountain AE API |
| REQ ID | The 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.
| Field | Description |
|---|---|
| Active archiving | Yes/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:
- Locate the desired revision in the table
- Click the "Archive" button next to it
- The system sends the PDF file to IronMountain AE via the API
- 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
| Aspect | IronMountain M-Files | IronMountain AE |
|---|---|---|
| Platform | M-Files CloudVault | IronMountain Archive Engine |
| Connection protocol | REST API with session token (username + password + vault GUID) | API with PRO + static Token + REQ ID |
| Archiving condition | Approved/archived PDF revision, configured document type | Approved/archived PDF revision, with electronic signatures, configured document type |
| Document type mapping | Requires an M-Files document ID per document type | No additional ID required |
| Connection validation | Obtaining an authentication token | Connectivity check call |