> 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/devops/organizations/individual-organizations/using-an-organizations-components-tab.md).

# Using an Organization's Components Tab

## ![](https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FG5ZbxX918xOHwbAwAJ4n%2FSummary2-Small-Icon.svg?alt=media\&token=da26a67f-ff7f-47b3-8669-06be960dc2d7) Overview

This article shows you how to use the Components tab to view and filter an organization's components.

{% hint style="info" %}
An organization's components are retrieved automatically, and you do not need to retrieve them manually unless you need changes to a component to be reflected immediately.
{% endhint %}

## Using the Components Tab

{% stepper %}
{% step %}

### Select Organization

1. Click **Organizations** from the left sidebar menu.
2. Click the organization to view an overview of.

   <div align="left"><figure><img src="https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FfUPti0jnb0MqB6rvD5qs%2FUsingAnOrganizationsComponentsTab-S01-01.png?alt=media&amp;token=f7c62ec3-089c-49e2-96d7-d72eeac99051" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

### View Components

The **Components** tab provides a searchable, filterable list of all the organization's components retrieved by DevOps.

<div align="left"><figure><img src="https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FhA4g0sKyF2uMlr0lPLCJ%2FUsingAnOrganizationsComponentsTab-S02-01.png?alt=media&amp;token=bb559d33-4f20-4d69-9520-7ebc9ba02834" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
If the components have changed since the last retrieval, you must run a manual **Retrieve** to view the latest updates.
{% endhint %}

The table below explains the information shown in each column of the **Components** table.

<table><thead><tr><th width="179.6666259765625">Column</th><th>Description</th></tr></thead><tbody><tr><td><strong>Component</strong></td><td>The component name and type.</td></tr><tr><td><strong>Created</strong></td><td>The DevOps user who last interacted with this component, along with the time since that interaction. The System User (SU) represents automated processes such as retrievals and pipelines.</td></tr><tr><td><strong>SF Updated</strong></td><td>The name of the user account and the time and date of the last Salesforce component modification.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Filter Components

You can filter and sort the list of components to find what you need. The table below explains what each filter does. Multiple filters can be used together.

{% hint style="info" %}
To quickly remove all filters, refresh the browser page.
{% endhint %}

<table><thead><tr><th width="159.66668701171875">Filter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Users</strong></td><td>Filter by two groups of users: Flosum Cloud Apps users (<strong>Created by</strong>) and Salesforce users (<strong>SF updated by</strong>). You can select multiple users from each group.</td></tr><tr><td><strong>Type</strong></td><td>Filter components by type. You can search for types and pick more than one.</td></tr><tr><td><strong>Time</strong></td><td>Filter components by when they were last updated, using either time field: <strong>Created by</strong> time or <strong>SF updated by</strong> time. You can set a date range with the date picker by clicking <strong>Specific date</strong>.</td></tr><tr><td><strong>Search</strong></td><td>Search for components by <strong>Name</strong>.</td></tr><tr><td><strong>Sort</strong></td><td>Sort components by the <strong>Component</strong>, <strong>Created</strong>, or <strong>SF Updated</strong> columns.</td></tr></tbody></table>
{% endstep %}

{% step %}

### View Component Details

You can view the details of each component. These details reflect only the last retrieval, so if the component has changed in Salesforce since then, you must manually **Retrieve** it to see the current details.

1. Click a component to view.

   <div align="left"><figure><img src="https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FtanBv8GoV4wadhZxSpko%2FUsingAnOrganizationsComponentsTab-S04-01.png?alt=media&amp;token=5a0ae1c3-3152-4b73-8279-2a2b28eccacb" alt="" width="563"><figcaption></figcaption></figure></div>
2. Scroll to view the details of the component.

   <div align="left"><figure><img src="https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FQK3xhsDmha9wnPQHsg4W%2FUsingAnOrganizationsComponentsTab-S04-02.png?alt=media&amp;token=dea65ffa-cd68-45b4-a50c-18c9f83ab78c" 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 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/devops/organizations/individual-organizations/using-an-organizations-components-tab.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.