> 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.9-monthly-release-notes.md). # Backup & Archive (v4.6.9) - Monthly Release Notes {% hint style="info" %} #### Release Details - Backup & Archive - v4.6.9 - April 20, 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 patch release for **Backup & Archive (v4.6.9)**. This release introduces a set of new Custom Permissions for the Backup & Archive Salesforce package, giving administrators fine-grained control over which users can view and interact with key components. These permissions help organizations align Backup & Archive usage with internal compliance and data governance policies. ### ![](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) Custom Permissions for Backup & Archive Salesforce Package This release adds a new set of **Custom Permissions** to the Backup & Archive Salesforce package. Administrators can now individually control visibility and execution rights for the following Backup & Archive components and actions: * Search * Time Machine * Related Archives * Unarchive * Backup History Each permission can be assigned through Permission Sets or Profiles, allowing you to tailor access to match specific user roles and responsibilities. The following Custom Permissions are now available: * **View Search List**: Grants access to the Search component view (Search List). Enable this permission for users who need to review Search job results but do not need to start new ones. * **Execute Search**: Allows users to run Search jobs against backed-up data. Enable this permission only for users who are authorized to initiate Search operations, as these jobs can be resource-intensive and expose sensitive data. * **View Time Machine**: Grants access to the Time Machine component, allowing users to view historical versions of records and navigate point-in-time snapshots. Grant this permission only to users who require access to record history exploration, such as auditors or senior administrators. * **View Related Archives**: Allows users to view archived records related to a specific Salesforce record within the Related Archives component. This controls whether related archived data is surfaced in the record context, helping limit exposure of historical data to authorized users only. * **View Backup History**: Grants access to the Backup History component. Enable this permission for users who need visibility into previously backed-up data and backup job outcomes. By default, these permissions are not granted to any user. Assign them through Permission Sets or Profiles as part of your Backup & Archive access model to ensure users only see and act on the data and features appropriate to their role. --- # 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.9-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.