> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/vault/autorabit-vault-freemium/destination-org.md).

# Destination Org

## Reviewing destination org connection status and org details from the AutoRABIT Vault Dashboard

## Starting Context

The flow begins after the source org and destination org are registered and authenticated in AutoRABIT Vault. The Dashboard displays the connected org indicators at the top of the page, along with the available AutoRABIT Vault actions and usage summaries.

{% hint style="info" %}
**Note:** The values displayed for the destination org depend on the connected Salesforce environment and remain specific to the selected org.
{% endhint %}

## Destination Org Status on the Dashboard

The Dashboard shows both Source Org and Destination Org connection indicators near the page header. The Destination Org indicator confirms that the destination Salesforce org is connected and ready for AutoRABIT Vault workflows. The Re-authenticate action remains available beside the org indicator to refresh the connection when required.

The rest of the Dashboard continues to show key AutoRABIT Vault areas, including Backup Configs, Backup Jobs, Restore Jobs, Replicate Jobs, storage usage, and Recommended Actions. These sections provide the next operational paths after org registration is complete.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FrEMfGlpQoPFhKe4hJqNn%2F1.png?alt=media&amp;token=3b930f75-3630-42c1-a1e1-d0dc4f695c27" alt=""><figcaption></figcaption></figure>

## Review Destination Org Details

Selecting the Destination Org indicator opens the Destination org details dialog. The dialog displays the registered destination org information in a read-only view, including Org name, Username, Org ID, API version, Instance URL, Environment type, Platform, Org edition, Auth type, and Registered details.

This information helps confirm that AutoRABIT Vault is connected to the intended destination org before backup, restore, replication, or related data operations proceed. The displayed values reflect the authenticated Salesforce destination org and are not edited from this dialog.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FF51IKQHD7rZh4dhlOOT9%2F2.png?alt=media&amp;token=391540f3-cd1e-47fa-9fc3-8ed4275b3381" alt=""><figcaption></figcaption></figure>

## Close the Details Dialog

The Close action dismisses the Destination org details dialog and returns to the Dashboard. The connected destination org status remains visible in the header, and the Dashboard remains available for the next AutoRABIT Vault workflow.

## System Behavior

* AutoRABIT Vault displays the Destination Org indicator only after the destination org is connected.
* The Destination org details dialog provides read-only information about the registered destination org.
* Re-authenticate remains available when the org connection must be refreshed.
* Closing the dialog does not change org registration, authentication, or Dashboard state.

## Final Result

After the destination org details are reviewed, the Dashboard confirms that the destination org remains connected and ready for downstream AutoRABIT Vault operations. The flow ends with the Dashboard available for backup, restore, replication, or other configured actions.


---

# 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://knowledgebase.autorabit.com/product-guides/vault/autorabit-vault-freemium/destination-org.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.
