> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-core/records-archival.md).
# Records Archival
## Archival Process
The archival process manages historical data by archiving older records while retaining essential recent data. Multiple archival jobs are available, and their configurations can be adjusted under Global Settings with key named **`Archival Policies`**. Users can modify these settings based on their requirements.
## Archival Policies
### Application Scans
1. **`Retention Period`**: 7 days (default value)
2. Retention Type can either be configured based on number of days or scans
| Retention Type | Description |
| --------------------- | ------------------------------------------------------------------------------- |
| numberOfDaysToRetain | Number of days the scan history will be retained unless exempted from archival. |
| numberOfScansToRetain | Number of previous scans to retained unless exempted from archival. |
1. **`Archival Rule`**: Scan history will be maintained for 7 days. Any scans older than 7 days will be archived, except for the latest scan.
2. **`Exemptions`**: Users can mark specific scans as exempt from the archival process to retain them beyond the default period.
3. To exclude a scan from archival, Navigate to the required application’s actions -> **`View Previous Scans`** and exclude / include the required scan from archival
### Job Executions
1. **`Retention Period`**: 7 days (default value)
2. **`Archival Rule`**:
1. One-time jobs that are completed will be retained for 7 days.
2. Any job executions older than 7 days will be archived.
3. Recurring jobs are not subject to archival and will remain available.
### Audit Log
1. **`Retention Period`**: 30 days (default value)
2. **`Archival Rule`**: System and user audit logs will be maintained for 30 days. Any records older than 30 days will be archived.
### Notification
1. **`Retention Period`**: 30 days (default value)
2. **`Archival Rule`**: Notification Status logs will be maintained for 30 days. Any records older than 30 days will be archived.
### Configuring Archival Policies
Users can modify the archival settings by navigating to **`Global Settings`** > **`Archival Policies`**. These settings allow customization of retention periods and exemption rules based on organizational needs. Archival settings are customer-configurable for paid subscriptions only. Data processed under Free Services is subject to the maximum retention period stated in [Integral Zone Free Services — Scope, Limits & Data Retention](/product-guides/integral-zone/iz-free-services.md), which cannot be extended, reconfigured, or exempted from archival.
### Additional Considerations
1. Archived data is no longer accessible through regular system views but can be retrieved if needed.
2. Proper exemptions should be configured to retain critical scan data beyond the archival window.
3. Recurring jobs remain available regardless of their execution history.
### See Also
* [Creating an Agent](/product-guides/integral-zone/iz-suite/iz-core/agent/create-agent.md)
* [Updating an Agent](/product-guides/integral-zone/iz-suite/iz-core/agent/update-agent.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-core/records-archival.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
