> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/release-notes/backup-and-archive/monthly-releases/backup-and-archive-v4.6.13-monthly-release-notes.md).

# Backup & Archive (v4.6.13) - Monthly Release Notes

{% hint style="info" %}

#### Release Details - Backup & Archive - v4.6.13 - May 26, 2026

This article is intended for Salesforce administrators, compliance officers, and IT teams responsible for managing Salesforce backups and data governance.

**Release Type**

* Monthly
* Applies to Flosum-hosted and self-hosted

**Prerequisites**

* A registered and configured Flosum Cloud Apps tenant
* Appropriate Flosum user permissions (SystemAdministrator or equivalent)
  {% endhint %}

## ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FPL2eaOdTi7VscAjFymsv%2FSummary2-Small-Icon.svg?alt=media\&token=a14ffcd6-66df-43ec-aafc-61364d19c7cd) Summary

This article documents the monthly release for **Backup & Archive (v4.6.13)**. This release introduces the public Backup & Archive API and Global Settings API, and adds a configurable Retention Policy that automates the removal of aged backup and archive data at the organization level.

### ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FgG2A2IRhOXknRFbAGToW%2FNew-Feature-Icon2-Small.svg?alt=media\&token=76ce09b1-243a-482d-97e4-ccc4cbc94d67) External API Access

This release introduces the public **Backup & Archive API** and **Global Settings API** endpoints, enabling customers to integrate Backup & Archive directly into their own workflows, automation pipelines, and downstream systems.

With public API access, administrators and developers can:

* Start and monitor backup and archive jobs.
* Create and manage scheduled backup and archive jobs.
* Embed Backup & Archive functionality into third-party tooling and internal applications.

For endpoint specifications, authentication requirements, and request/response schemas, see the official API Documentation.

* [API Quickstart](/api/api-quickstart.md)

### ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FgG2A2IRhOXknRFbAGToW%2FNew-Feature-Icon2-Small.svg?alt=media\&token=76ce09b1-243a-482d-97e4-ccc4cbc94d67) Retention Policy

Retention Policy allows users to automate the removal of backed-up and archived data after a configured period. This helps control storage growth and aligns data lifecycles with internal governance and compliance requirements, without the risk of accidental data loss from manual cleanup.

Retention Policy is configured per organization under **Organization Settings**. See the following article to learn more about Retention Policies and how to add them.

* [Changing Retention Policy Settings](/backup-and-archive/settings/organization-settings/changing-retention-policy-settings.md)

**Two retention windows can be configured independently:**

* **Backup Keep For**: Defines the retention window for backup data. Versions older than this period become eligible for automatic deletion.
* **Archive Keep For**: Defines the retention window for archival data. Versions older than this period become eligible for automatic deletion.

{% hint style="warning" %}

#### Two Records Retained

Regardless of the configured retention period, the system always retains the two most recent versions of any record. This helps prevent data loss from accidental deletions or data corruptions.
{% endhint %}


---

# 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://docs.flosum.com/release-notes/backup-and-archive/monthly-releases/backup-and-archive-v4.6.13-monthly-release-notes.md?ask=<question>&goal=<user_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.