> 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/getting-started/what-is-boza.md).

# What is Boza?

Boza is an IT cockpit designed to help organizations manage their software and SaaS portfolios. It gives IT teams full visibility into the tools used across the company, while providing employees with a smoother experience for accessing and managing their applications.

The whole product is available in **French and English**: a workspace Admin chooses the language once, and the interface and every email Boza sends follow it.

***

## For IT Managers and CIOs

Boza equips IT leaders with the tools they need to take control of their software landscape:

* **Map and track SaaS usage** across the entire organization
* **Reduce costs** by identifying unused licenses, redundant subscriptions, and optimization opportunities
* **Strengthen security** by detecting shadow IT and enforcing approval workflows
* **Automate routine tasks** such as onboarding, offboarding, and access management
* **Gain actionable insights** through dashboards and reports on software spend, usage trends, and compliance

<figure><img src="https://1674559363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvSdGShklbloRzyUwwMzX%2Fuploads%2Fgit-blob-e54b31b49e21fa59141297cd06d8e075610ad5eb%2Fboza-dashboard.png?alt=media" alt="Boza Dashboard showing KPI cards, most used apps, and cost trends"><figcaption></figcaption></figure>

## For Employees

Boza also improves the day-to-day experience for every team member:

* **Seamless access** to approved tools and applications
* **Share feedback** and rate satisfaction with the tools they use
* **Simplified access requests** to get new software through a structured, transparent process

***

## How Boza Collects Data

Boza follows a strict data minimization approach:

* Only **strictly necessary data** is collected to discover and monitor SaaS tools
* No unnecessary or excessive data is gathered
* Data is **automatically anonymized** where applicable

***

## Application Catalog

Boza maintains a catalog of **over 100,000 applications** worldwide. The catalog is continuously updated to ensure accurate identification and classification of the tools your organization uses.

***

## Requirements

To get started with Boza, your organization needs:

* **Identity Provider**: Google Workspace or Microsoft Entra ID
* **Supported browsers**: Google Chrome, Microsoft Edge, or Mozilla Firefox
* **Web-based application usage** within the organization

## Authentication Methods

Users can sign in to Boza using:

* **Google SSO** (for Google Workspace environments)
* **Microsoft SSO** (for Microsoft Entra ID environments)


---

# 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/getting-started/what-is-boza.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.
