> For the complete documentation index, see [llms.txt](https://boza.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boza.gitbook.io/docs/inventory/applications/authorization-categories.md).

# Authorization Categories

Use application approval status to separate managed software from tools that your organization has rejected or has not yet reviewed.

## Where Applications Appear

Boza uses two inventory tabs and one separate triage page:

| Location                           | What appears there                                                    |
| ---------------------------------- | --------------------------------------------------------------------- |
| **Applications → My Apps**         | Applications marked **Approved** or **Under Review**                  |
| **Applications → Unapproved Apps** | Applications marked **Unapproved**                                    |
| **Shadow IT**                      | Newly detected applications that do not have an approval decision yet |

Approval status and tracking are separate. An application can remain tracked while it is under review or unapproved, allowing your team to investigate usage before deciding what to do.

## My Apps

**My Apps** is the working inventory for applications your organization has approved or is actively reviewing.

For an important approved application, complete:

* A Super Admin and any additional application owners.
* An Access Reviewer if the app is in scope for certification campaigns.
* Tracking status, vendor, lifecycle, criticality, and security information.
* Subscription, license, cost, and renewal information.

## Unapproved Apps

**Unapproved Apps** contains applications your organization has explicitly classified as unapproved. These can include employee-created accounts, unsanctioned trials, duplicated tools, or software that did not pass review.

An unapproved application can remain tracked while you investigate it. Marking it unapproved does not automatically remove access from employees or block the service.

{% hint style="warning" %}
Changing approval status is a Boza inventory decision. It does not disable the application in its own admin console or identity provider.
{% endhint %}

## Shadow IT

[Shadow IT](/docs/inventory/shadow-it.md) is the intake queue for applications discovered through supported browser, identity-provider, integration, invoice, or other signals before an administrator classifies them.

From the dedicated page, an administrator can:

* **Approve** the application and move it to **My Apps**.
* **Unapprove** it and move it to **Unapproved Apps**.
* Delete a false positive or irrelevant discovery.

## How Applications Move

1. Boza detects a new application and puts it in **Shadow IT**.
2. An administrator reviews its source and affected users.
3. The administrator approves, unapproves, or deletes the discovery.
4. The approval status can later be changed from the [App Detail Page](/docs/inventory/applications/app-detail.md).

You can also click **Add New App** on Applications to create an inventory record directly. This is useful for internal, on-premise, or otherwise undiscoverable software.

## Related Guides

* [Applications](/docs/inventory/applications.md)
* [Shadow IT](/docs/inventory/shadow-it.md)
* [App Detail Page](/docs/inventory/applications/app-detail.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://boza.gitbook.io/docs/inventory/applications/authorization-categories.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.