> 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/backup-and-archive/settings/disabling-scheduled-backups-and-archives.md).
# Disabling Scheduled Backups and Archives
{% hint style="success" %}
#### Required User Credentials
\[**Flosum User**] - **Backup & Archive** license with **App Settings** permissions
{% endhint %}
## Overview
You can disable scheduled backups and archives individually for each Salesforce Organization. By default, both are enabled. Scheduled backups and scheduled archives can be controlled separately. When set to **Disabled**, no system-scheduled or user-scheduled operations will run. This article shows you how to disable backups for an organization.
{% hint style="info" %}
For simplicity, this article refers to backups and archives as "backups/archives." Since scheduled backups and scheduled archives can be disabled independently, you can choose to disable either one or both.
{% endhint %}
## Disable Scheduled Backups/Archives
{% stepper %}
{% step %}
### Disable
{% hint style="info" %}
Disabling scheduled backups/archives affects both system-scheduled and user-scheduled backups/archives.
{% endhint %}
1. Click **Settings** from the sidebar menu.
2. Click the **Organization** to disable schedules for.
3. On the **General** tab, scroll down to the **Manage Operations** section.
4. Click the **Scheduled backups** and/or **Scheduled archives** toggle to change from **Enabled** to **Disabled**.
5. Click **Save**.
{% endstep %}
{% step %}
### Verify
1. Click **Backup & Archive** from the sidebar menu.
2. Click the **Schedule** tab.
3. Confirm that a warning about disabled scheduled backups/archives appears.
{% endstep %}
{% endstepper %}
---
# 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/backup-and-archive/settings/disabling-scheduled-backups-and-archives.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.
