> 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/organization-settings/backup-and-archive-settings-general-settings.md).
# Changing General Settings
{% hint style="success" %}
#### Required User Credentials
\[**Flosum User**] - **Backup & Archive** license with **App Settings** permissions
{% endhint %}
## Overview
Each of your Salesforce Organizations has its own **Settings** page that can be configured independently. The **Settings** page is divided into three tabs: **General**, **Notifications**, and **Integrations**. This article focuses on the settings within the **General** tab. For instructions on the other tabs, refer to the following article.
* [Changing Notifications Settings](/backup-and-archive/settings/organization-settings/backup-and-archive-settings-notifications.md)
* [Changing Integrations Settings](/backup-and-archive/settings/organization-settings/backup-and-archive-settings-integrations.md)
The **General** Settings tab lets you review your organization settings, manage backup and archive operations, and set API quotas.
## General Settings
{% stepper %}
{% step %}
### Access General Settings
Below are instructions for accessing the General Settings and a brief overview of each section.
1. Click **Settings** from the sidebar menu.
2. Click the **Organization** to change settings for.
3. Click the **General** tab.
{% endstep %}
{% step %}
### Organization Details
The **Organization Details** section lists details about the connection between your Flosum Backup & Archive tenant and your Salesforce org.
{% endstep %}
{% step %}
### Manage Operations
Flosum automatically enables scheduled backups and archives by default, providing restore points in case of data loss. You can manage backup and archive scheduling separately using the **Scheduled backups** and **Scheduled archives** toggles. When either toggle is disabled, existing schedules of that type won't run, and you won't be able to create new ones. For more details about disabling schedules, see the following article:
* [Disabling Scheduled Backups and Archives](/backup-and-archive/settings/disabling-scheduled-backups-and-archives.md)
* If you make changes, click **Save** to apply them.
{% endstep %}
{% step %}
### API Quota
Salesforce enforces daily API call usage limits to prevent individual customers from overusing its Point of Deployment (PoD) resources. By default, Flosum sets the maximum **REST API** and **Bulk API** calls to 80% of the Salesforce limits. This approach ensures your backup and archive jobs operate within the allowable range while reserving capacity for other API operations. As a best practice, maintain these 80% thresholds to leave room for other API calls and avoid job suspension when daily API limits are reached. These percentages can be adjusted if necessary, though caution is advised.
* If you make changes, click **Save** to apply them.
{% 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/organization-settings/backup-and-archive-settings-general-settings.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.
