> For the complete documentation index, see [llms.txt](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/labels-and-applications.md). # Labels and Applications for Access Reviews ## Overview Labels and Application names in Access Reviews are distinct, yet similar, classification tools that help keep large Access Review programs manageable at scale. You apply them to configurations and reviews to filter, report, and control notifications based on your review program. * **Labels** are free-form tags you create and apply to configurations or individual reviews. Use a label for any property you want to group similar reviews by, such as the applicable compliance program, business unit, environment, or review cycle. Labels applied at the configuration level are inherited by all reviews created from that configuration. * **Application** names identify the application, platform type, or system a review targets, such as AWS S3, Active Directory, Salesforce, or Workday. You assign an application name only at the review configuration level; every review created from the configuration inherits it. This makes it easy to report on all reviews related to a specific application, platform, or system. {% hint style="info" %} Veza surfaces these as two separate components, **Labels** and **Applications**, each on its own tab under **Access Reviews** > **Settings**. {% endhint %} Neither attribute changes the scope, assigned reviewers, or individual decisions in a review. They affect only how configurations and reviews are organized, filtered, and reported on. ## Common use cases * **Review a full application program:** Assign the **ServiceNow** application name to every configuration that reviews ServiceNow access. Operators can then filter the Configurations and Access Reviews pages to the complete ServiceNow recertification program. * **Track a compliance program:** Apply a `SOC 2` or `HIPAA` label to the configurations that support a compliance program, so auditors can find the relevant reviews without searching through unrelated campaigns. * **Separate campaigns by cycle:** Apply a `Q3 2026` label to a quarterly campaign so each cycle's reviews stay distinct and easy to report on. * **Suppress notifications for a subset:** Apply a label such as `test` to low-priority reviews, then exclude that label from digest and alert emails. See [Configure Notification Exclusions](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/configure-notification-exclusions.md). ## Manage labels and applications Manage labels and applications centrally under **Access Reviews** > **Settings**, on the **Labels** and **Applications** tabs. Creating, renaming, and deleting entries requires an Access Reviews administrator or a Veza administrator; operators do not see these tabs, though they can apply existing labels and applications (see [Apply labels and applications](#apply-labels-and-applications)). * **Labels** tab ("Manage the labels used in reviews and configurations"): create, rename, and delete labels. * **Applications** tab ("Manage the applications used in reviews and configurations"): create, rename, and delete application entries. {% hint style="info" %} Renaming a label or application updates it everywhere it is currently applied. Deleting one removes it from every configuration and review it was applied to. {% endhint %} ## Apply labels and applications ### Labels Apply labels to a configuration or to an individual review: * **On a configuration:** when [creating](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/review-configuration.md) or [editing](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/edit-configuration.md) a configuration, use the **Labels** field ("Assign labels to reviews created from this configuration"). Select existing labels or create new ones inline. * **On a review:** when [creating a review](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/create-access-review.md), use the **Labels** field ("Assign labels to this review"). A review created from a labeled configuration inherits that configuration's labels. You can add more labels to the individual review on top of the inherited ones. ### Applications Assign applications to a configuration when [creating](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/review-configuration.md) or [editing](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/edit-configuration.md) it, using the **Applications** field ("Assign applications to reviews created from this configuration"). Reviews created from the configuration take their applications from it. {% hint style="info" %} Applications are assigned only at the configuration level. There is no Applications field when creating an individual review; a review inherits its applications from its configuration. {% endhint %} ## Filter by label or application The Configurations page and the Access Reviews page both provide **Labels** and **Applications** filters and columns. Use them to narrow a long list to the configurations or reviews for a given application, compliance program, or campaign: * Go to **Access Reviews** > **Configurations** and apply the **Labels** or **Applications** filter. * Go to **Access Reviews** > **Access Reviews** and apply the **Labels** or **Applications** filter. When you select more than one label or application name in a filter, choose **Any Selected** to return configurations or reviews that carry at least one of the selected values, or **All Selected** to return only those that carry every selected value. Filters default to **Any Selected**. Filter selections are saved in the page URL, so you can bookmark a filtered view or share it with teammates. See [Manage Access Reviews](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/manage-access-reviews.md) for more on the list pages. ## Scope consolidated reports by label Labels also select which reviews a consolidated report covers. On the Access Reviews page, choose **Export** > **Generate report (Excel)** to open the **Create Report** dialog. Under **Reviews in this report**, select reviews with the **Labels**, **Review Status**, and **Date Completed** filters. For example, you can produce one report covering every completed review labeled `SOC 2`. Veza emails the report to the recipients you specify. See [Manage Access Reviews](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/manage-access-reviews.md#exporting-reviews-to-csv) for more on exporting reviews. ## See also * [Access Reviews Global Settings](/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/access-review-settings.md) * [Create a Configuration](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/review-configuration.md) * [Create a Review](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/create-access-review.md) * [Manage Access Reviews](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/manage-access-reviews.md) * [Configure Notification Exclusions](/4yItIzMvkpAvMVFAamTf/features/access-reviews/how-to/configure-notification-exclusions.md) --- # 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.veza.com/4yItIzMvkpAvMVFAamTf/features/access-reviews/configuration/labels-and-applications.md?ask=&goal= ``` `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.