> 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.8.2-monthly-release-notes.md). # Backup & Archive (v4.8.2) - Monthly Release Notes {% hint style="info" %} #### Release Details - Backup & Archive - v4.8.2 - September 29, 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.8.2)**. This release adds a Backup Coverage Report and a Salesforce permission check, so you can see which objects in a connected organization are covered and whether missing permissions are the reason an object is absent. It also adds bulk unarchive for archived related records in the Backup & Archive Salesforce Package, so you can restore several related records in one action. Both changes reduce the manual checking needed to confirm what is protected and to bring archived data back. ### ![](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) Backup Coverage Report and Salesforce Permission Check #### What Changed **Backup & Archive** now gives you more visibility into Salesforce permissions and backup coverage for your connected organizations. You can: * Check whether the Salesforce integration user has the recommended **Modify All Data** and **Query All Files** permissions. * View a **Backup Coverage Report** for a connected Salesforce organization. * See which Salesforce objects are currently covered by Backup & Archive. * Identify objects that Backup & Archive does not support. * Identify objects that may not be available because of missing Salesforce permissions. * See objects that are explicitly excluded in your backup settings.
#### Why It Was Done A Salesforce organization can connect successfully even when the integration user does not have enough permissions to reach all of the available Salesforce data. Previously, it was difficult to tell whether missing permissions or Backup & Archive support rules were the reason an object did not appear in backups. The report makes the current coverage visible and helps you find gaps that come down to permissions. #### What You Will Notice The Organization List may show a permission warning when the connected Salesforce user is missing **Modify All Data** or **Query All Files**. A new Salesforce Permissions section in Organization Settings holds the object-level Backup Coverage Report. For each Salesforce object, the report shows a status:
StatusWhat it means
Backed UpThe object is available and supported by Backup & Archive.
Not SupportedBackup & Archive does not support the object.
Missing PermissionsThe object is visible in Salesforce metadata but is not available to the integration user.
ExcludedThe object is explicitly excluded in your backup settings.
The report is generated on demand, so it reflects your current Salesforce permissions, metadata, and Backup & Archive configuration. {% hint style="info" %} **Important** The report provides object-level coverage only. It does not currently provide field-level coverage or historical coverage information. Having the recommended Salesforce permissions does not guarantee that every Salesforce object is backed up, because some objects are unsupported, explicitly excluded, or subject to Salesforce API limitations. {% endhint %} ### ![](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) Salesforce Package: Bulk Unarchive for Archived Related Records #### What Changed The **Backup & Archive Salesforce Package** now supports bulk unarchiving for archived related records. You can: * Select multiple archived related records directly from the list view. * Unarchive all of the selected records with a single `Unarchive` action. * Process multiple records in one operation instead of restoring them individually. * See which records succeeded and which failed when an operation only partly completes. #### Why It Was Done Previously, archived related records could only be unarchived one at a time from the record details page. If an Account had several archived Contacts, you had to open each Contact and unarchive it separately. Selecting and restoring several archived related records at once removes that repetition. #### What You Will Notice When you view archived related records in a list, you can select one or more of them with checkboxes. The `Unarchive` action becomes available as soon as at least one record is selected. After you start the action: * A loading indicator appears while the records are processed. * The selected records are unarchived in a single bulk operation. * The list refreshes when processing finishes. * Records that were unarchived successfully return to an active state. * If some records cannot be unarchived, you receive a summary of the successful and failed operations. * Permission and validation errors are shown for the records that could not be restored. The existing single-record unarchive action remains available. #### Availability This feature is in version 2.5 of the Backup & Archive Salesforce Package. Install or upgrade to that version to use it. For the steps, see [Installing or Upgrading The Salesforce Package](/backup-and-archive/backup-and-archive-in-salesforce/installing-or-upgrading-the-salesforce-package.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://docs.flosum.com/release-notes/backup-and-archive/monthly-releases/backup-and-archive-v4.8.2-monthly-release-notes.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.