> 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/audit-and-compliance/viewing-component-audit-status.md).

# Viewing Component Audit Status

## ![](https://3321997875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpieUdPB8n4L2gG8EYRy%2Fuploads%2F0pk52bJqKVUJPTPVPhiw%2FSummary2-Small-Icon.svg?alt=media\&token=74913d54-0cfd-4703-aa56-af396629dc59) Overview

This article explains how to find the components within an organization and read the audit status of each. The **Components** tab lists every component returned by the most recent audit, along with the Salesforce user who last modified it, when it was last updated in Salesforce, and whether the change came through Flosum DevOps or was made directly in the Salesforce org. Filters and a search box help narrow the list to the components you need.

{% hint style="info" %}
The table shows everything the audit records for each component. Clicking a component does not show additional details.
{% endhint %}

### Component Audit Statuses

Each audit first retrieves the components from the Salesforce org, then compares each component's last modified date and user with the Flosum DevOps deployments made to that org. That comparison determines the component's status. The table below explains what each status means.

{% hint style="warning" %}

#### Deleted Components

An audit job reports only **Soft Deleted** components (those moved to the Recycle Bin) as deleted. Once a component is **Permanently Deleted**, it no longer appears in the component list.
{% endhint %}

<table><thead><tr><th width="250.00006103515625">Status</th><th>Description</th></tr></thead><tbody><tr><td><strong>Updated via branch</strong></td><td>A Flosum DevOps deployment matches the component's last modified date and user. The status names the branch that delivered the change.</td></tr><tr><td><strong>Updated directly in Salesforce</strong></td><td>No Flosum DevOps deployment matches the component's last modified date and user. The component was changed directly in the Salesforce org or deployed from another source.</td></tr><tr><td><strong>Deleted via branch</strong></td><td>The component was deleted through Destructive Changes in Flosum DevOps. The status names the branch that removed it.</td></tr><tr><td><strong>Deleted directly in Salesforce</strong></td><td>The component was deleted directly in the Salesforce org or through a third-party tool.</td></tr></tbody></table>

## Components Table

{% stepper %}
{% step %}

### Access Components

1. Click **Organizations** from the left sidebar menu.&#x20;

   <div align="left"><figure><img src="https://3321997875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpieUdPB8n4L2gG8EYRy%2Fuploads%2FOJofo4HrEkzJdFUe9kWK%2FViewingComponentAuditStatus-S01-01.png?alt=media&amp;token=a1e22590-bb39-4c5e-a5bc-2a600956e3a7" alt="" width="563"><figcaption></figcaption></figure></div>
2. Click the **Components** tab.&#x20;

   <div align="left"><figure><img src="https://3321997875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpieUdPB8n4L2gG8EYRy%2Fuploads%2FEakYCe2HqhX2vm0r5CC2%2FViewingComponentAuditStatus-S01-02.png?alt=media&amp;token=e38222b7-fabd-4014-af6d-00573e05ac47" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

### Filter Components

The **Components** tab has four filters. By default, no filters are applied, and all components are displayed. The table below explains how each filter helps narrow the list of components.

<table><thead><tr><th width="179.666748046875">Filter</th><th>Description</th></tr></thead><tbody><tr><td><strong>All Users</strong></td><td>Filters the list by the Salesforce user who last modified the component. Select one or more.</td></tr><tr><td><strong>All Types</strong></td><td>Filters the list by metadata type, such as ApexClass, CustomField, or Layout. Select one or more.</td></tr><tr><td><strong>All Statuses</strong></td><td>Filters the list by component status. Select one or more.</td></tr><tr><td><strong>All Times</strong></td><td>Filters the list by the last update date of the component in Salesforce. <strong>Specific date</strong> opens a date picker for you to enter a custom date range.</td></tr></tbody></table>

<div align="left"><figure><img src="https://3321997875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpieUdPB8n4L2gG8EYRy%2Fuploads%2Fbb7Nfmxd1bcwgBpBKjCW%2FViewingComponentAuditStatus-S02-01.png?alt=media&amp;token=da768f2f-3bc7-4eb6-916a-cfd107bdd983" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Search Components

Use the search box to search by component name or type. You can combine the search with filters to narrow the list even more.

<div align="left"><figure><img src="https://3321997875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpieUdPB8n4L2gG8EYRy%2Fuploads%2FdC7jvVcRNPRBTJf2zvgp%2FViewingComponentAuditStatus-S03-01.png?alt=media&amp;token=cf1f971b-9925-4dad-a581-ffe81ac32a90" alt="" width="563"><figcaption></figcaption></figure></div>
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flosum.com/audit-and-compliance/viewing-component-audit-status.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.