> 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/general-information/how-custom-label-components-work.md).
# How Custom Label Components Work
##  Overview
DevOps now handles Salesforce **Custom Labels** as individual components. Previously, all custom labels in an organization were grouped together as a single **CustomLabels** component. With this change, you can retrieve, commit, and deploy only the labels you want, rather than all labels combined. This article shows the DevOps areas affected by this change to Custom Labels.
{% hint style="info" %}
If you have an existing **CustomLabels** component in your branch, you can continue to use it as before. However, when adding new components to a branch, you can add only individual custom labels.
{% endhint %}
## Custom Labels in DevOps
{% stepper %}
{% step %}
### Retrieve Components
When an organization's metadata is retrieved, the **CustomLabel** components are retrieved individually. You can filter the retrieved components to display only **CustomLabel** components. See the screenshot below. See the following articles for more general information about retrieving metadata and viewing retrieved components.
* [Retrieving Organization Metadata](/devops/organizations/individual-organizations/retrieving-organization-metadata.md)
* [Using an Organization's Components Tab](/devops/organizations/individual-organizations/using-an-organizations-components-tab.md)
{% endstep %}
{% step %}
### Add Components
Individual **CustomLabel** components can be added to a branch using the same steps as other components. The screenshot below shows a branch with three **CustomLabel** components. See the following article to learn how to add a component to a branch.
* [Adding Components to a Branch](/devops/code/branch-actions/adding-components-to-a-branch.md)
{% endstep %}
{% step %}
### Edit Components
Individual **CustomLabel** components can be edited directly in DevOps, just like other components. The screenshot below shows a **CustomLabel** open in the DevOps code editor.
{% endstep %}
{% step %}
### Deploy Components
Individual **CustomLabel** components can be deployed the same way as other components. The screenshot below shows the deployment of two of the three **CustomLabel** components. See the following article to learn how to deploy components to an organization.
* [Deploying a Branch](/devops/code/branch-actions/deploying-a-branch.md)
{% 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/general-information/how-custom-label-components-work.md?ask=&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.
