> 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/~/revisions/VLU9yPmP4DSTi9m5DU71/product-guides/arm-1/arm-features/deployment/monitor-deployments-1.md).

# Track Profile & Permissions Compare History

{% hint style="info" %}
The **Profile & Permissions Compare History** screen is best viewed when the zoom setting is set to **80%** on your Chrome/Firefox browser.
{% endhint %}

### Overview <a href="#overview" id="overview"></a>

\
The Profile Compare History page provides a centralized view of all profile and permission set comparison activities performed within ARM. This page helps administrators track what comparisons were created, between which Salesforce orgs, and by whom, making it easier to audit changes and manage historical comparisons.\ <br>

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FPb4sQLWPdgf9Z7KDBsVi%2FScreenshot%202026-02-04%20at%2010.33.41%E2%80%AFAM.png?alt=media&amp;token=b43887d4-7f4c-44ed-bd41-2b3e06c7dc3a" alt=""><figcaption></figcaption></figure>

**What you can do on this page**\
\
• View all profile and permission set comparison records created in ARM\
• Identify the source and target Salesforce orgs used for comparison\
• Track who created each comparison and when\
• Search, filter, and navigate through historical comparison entries\
• Delete comparison records that are no longer required

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FhYxoNDqRfwWhbX2tCI26%2Fimage.png?alt=media&amp;token=2877148f-5df9-472b-9ed8-a041743c9907" alt=""><figcaption></figcaption></figure>


---

# 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/~/revisions/VLU9yPmP4DSTi9m5DU71/product-guides/arm-1/arm-features/deployment/monitor-deployments-1.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.