> 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.6-monthly-release-notes.md). # Backup & Archive (v4.8.6) - Monthly Release Notes {% hint style="info" %} #### Release Details - Backup & Archive - v4.8.6 - October 13, 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.6)**. This release adds customer-managed Google Cloud Storage (GCS) buckets as a storage option. You configure the bucket in Global Settings, and Backup & Archive data is then stored in your own Google Cloud project, where you control the bucket and its access permissions. ### ![](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) Google Cloud Storage Support #### What Changed **Backup & Archive** now supports customer-managed Google Cloud Storage (GCS) buckets as a storage option. You configure a GCS bucket in **Global Settings** by providing your Google Cloud credentials and the bucket information. The integration uses two types of credentials: * **Service Account credentials:** for file operations through the Google Cloud API. * **HMAC credentials:** for access to Parquet backup data. See the following article for instructions on adding a GCS bucket. * [Adding a Google Cloud Storage Bucket for Storage](/global-settings/environment/storages/adding-a-google-cloud-storage-bucket-for-storage.md) #### Why It Was Done The new storage type lets you use your own Google Cloud infrastructure for Backup & Archive data, while you keep control over the storage bucket and its access permissions. #### What You Will Notice On the **Storages** page in Global Settings, **CREATE STORAGE** now offers **Google Cloud Storage** as a **Storage Type**. Along with a **Name** for the storage, the form asks for: * **Project ID**, **Client email**, and **Private key** from the service account's JSON key. * **HMAC access ID** and **HMAC secret**, from the service account's HMAC key. * **Bucket name**, the name of the target bucket. ![](https://content.gitbook.com/content/KdKbUdYCYQswKDxgzTfY/blobs/hw8QCLuQUeS40ch7MVhe/BA-Monthly-v4.8.6-GoogleCloudStorage-01-Glow.png) {% hint style="info" %} #### Important The bucket must already exist in your Google Cloud project, and the credentials must have the required permissions to access it. Adding a Google Cloud Storage configuration does not create a new bucket, and it does not migrate existing backup data to the new storage. {% 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.8.6-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.