> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/saas-data-monitoring/shadow-apps/google-shadow-apps/classify-shadow-apps.md).

# Classify shadow apps

Based on the [rich app data ](/docontrol-user-guide/saas-data-monitoring/shadow-apps/google-shadow-apps/app-discovery.md)and [risk scoring](/docontrol-user-guide/saas-data-monitoring/shadow-apps/google-shadow-apps/risk-snapshot.md) that DoControl provides, you can assess the potential risk of each application. After your evaluation, you can decide if the application is allowed (sanctioned), disallowed (unsanctioned), or banned (risky and unsanctioned), and classify accordingly.

Once apps are classified as sanctioned or unsanctioned, it's easy to manage and filter them, and gauge at a glance which applications follow organizational governance policies. 

You can classify shadow apps [one-by-one](#manual-classification) or [in bulk](#bulk-classification).

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FbwPQlMv2VF3e2IDPZhji%2Fclassify%20shadow%20apps.png?alt=media&amp;token=83a6eef8-c743-4fa2-9a57-a4df0ef8d451" alt=""><figcaption><p>Manually change the classification status of each shadow app to sanctioned, unsanctioned or banned</p></figcaption></figure>

## Manual classification

{% hint style="warning" %}
By default, each shadow app is unclassified. You need to manually change the classification status to **Sanctioned** (allowed), **Unsanctioned** (disallowed) or **Banned** (risky and disallowed).
{% endhint %}

1. In the DoControl sidebar, go to **Shadow apps > Google Workspace**.
2. Apply any relevant filters to narrow your display of shadow apps.
3. In the classification column, manually assign the relevant classification to each shadow app:
   * **Banned** - App is risky, and should **not** be installed in your organization's workspace.
   * **Sanctioned** - App use is allowed by your organization.
   * **Unclassified** - App isn't yet classified (this is the default classification).
   * **Unsanctioned** - App is installed, but **not** approved for use by your organization.

## Bulk classification

1. Go to **Shadow apps > Google Workspace**.
2. Apply any relevant filters to narrow your display of shadow apps.
3. Check the **All** checkbox next to the App name to select all displayed apps, or select the relevant apps.
4. Click the **Change classification** link to classify all selected apps in bulk.
5. Select the new classification: banned, sanctioned, unclassified, or unsanctioned.

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FoSbuJ7ZaOxsg6rgkLEEz%2Fbulk%20classification.png?alt=media&amp;token=b44e0e3b-64f8-4744-bb98-0d829c60bae4" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
To remove unsanctioned or banned apps from your organization's workspace, see [Google Workspace remediation](/docontrol-user-guide/workflows/define-workflow-settings/action-settings/remediate/google-workspace-remediation.md).
{% endhint %}


---

# 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.docontrol.io/docontrol-user-guide/saas-data-monitoring/shadow-apps/google-shadow-apps/classify-shadow-apps.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.