> 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/backup-and-archive-docs-ja/backup-and-archive/enable-direct-access-to-flosum-backup-and-archive-data.md).

# Flosum Backup & Archive データへのアクセスを有効化

## <img src="https://3874940933-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2Fgit-blob-3f6faa4230b72167926fbc0a31dd17dc7d74581d%2FSummary2-Small-Icon.svg?alt=media" alt="" data-size="original">概要

Salesforce 組織内で Flosum Backup & Archive のデータへのアクセスを有効にするには、Flosum グローバル設定と Salesforce 組織の両方を構成する必要があります。以下の記事では、この手順を案内します。

* [Flosum Backup & Archive データへのアクセスを有効にする](/global-settings/global-settings-docs-ja/sekyuriti/miapuri/flosum-backup-archive-dtahenoakusesuwonisuru.md)

アプリの構成が完了したら、Flosum Time Machine を使用してレコードを復元したり、Flosum Backup & Archive を使用して過去のレコードを検索したりできます。これらの機能の使用方法については、以下の記事を参照してください。

* [タイムマシンでレコードを復元する](/backup-and-archive/backup-and-archive-docs-ja/salesforce-deno-backup-archive/taimumashin/restoring-records-with-flosum-time-machine-in-salesforce.md)
* [Salesforce で Backup & Archive を検索する](/backup-and-archive/backup-and-archive-docs-ja/salesforce-deno-backup-archive/searching-with-flosum-backup-and-archive-in-salesforce.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/backup-and-archive/backup-and-archive-docs-ja/backup-and-archive/enable-direct-access-to-flosum-backup-and-archive-data.md?ask=<question>&goal=<user_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.
