> 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/platform/mapping.md).

# Business Capability Map

See which parts of your business each application supports, where several tools overlap, and where nothing is covered at all.

{% hint style="info" %}
**Beta.** The Business Capability Map is available to workspace Admins from **Mapping → Business Capability Map**. Generated structures and placements are drafts for you to confirm.
{% endhint %}

***

## Where It Lives

**Mapping** in the sidebar opens the **Diagrams** page. It offers four diagram types; only **Business Capability Map** is available today. Flow mapping, application matrix, and application life cycle are marked **Coming soon**.

***

## How the Map Is Built

The map has two levels: **capability groups** (for example, Finance or IT & Security) and the **capabilities** inside them. Applications are placed on capabilities.

Boza generates it in two confirmed steps, so you review a short structure before hundreds of applications are placed against it.

### Step 1 — draft and confirm the capability structure

1. Open **Mapping → Business Capability Map** and click **Get Started**.
2. Answer the questionnaire:
   * your industry or sector;
   * your business model;
   * your company size, which sets how granular the map should be;
   * your main business functions;
   * the compliance frameworks you follow;
   * documents describing your organization, such as policies or process maps;
   * anything else about your company, and the language capability names should use.
3. Click **Generate structure**.
4. Review the draft. A **Step 1 of 2** banner reports how many capability groups and capabilities were created. Rename, add, move, or remove them until the structure matches your business.

**Expected result:** the structure is on screen and the banner offers **Populate map**.

### Step 2 — place your applications

1. Click **Populate map**.
2. Choose how careful Boza should be:
   * **Place every app** — maps all your applications, best guess included, for you to correct afterwards. Recommended.
   * **Only confident matches** — places high-confidence applications and leaves the rest unmapped for you.
3. Optionally describe anything unusual about how your team uses its tools, for example *We use Notion as our CRM, not for docs*.
4. Click **Populate map**.

Placement runs in the background. The map stays readable while it runs, and editing resumes when it finishes.

{% hint style="info" %}
Only applications Boza already tracks can be placed. If placement stops before it finishes, everything already placed is kept and **Try again** picks up only the applications still missing.
{% endhint %}

***

## Work with the Map

| Action                               | How                                                                                                                         |
| ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------- |
| **Move an application**              | Drag its grip handle onto another capability                                                                                |
| **Add applications to a capability** | Open the capability and choose the tracked applications to add                                                              |
| **Inspect a placement**              | Click an application to open its panel — where it sits, why it was placed there, its confidence, and the features behind it |
| **Confirm placements**               | Confirm one application at a time, confirm a whole capability, or use **Confirm all**                                       |
| **Review the uncertain ones**        | Click the **to review** count to open a queue ordered with the most important placements first                              |
| **Highlight risk**                   | Click **at risk** to highlight business-critical applications without enforced SSO or MFA, or flagged as GDPR non-compliant |
| **Highlight renewals**               | Click **renewals** to highlight applications renewing soon                                                                  |
| **Export**                           | **Export → Export as PDF** for the visual map, or **Export as CSV** for the underlying rows                                 |

Applications that are not placed sit in an **Unmapped** column beside the map. Drag one onto a capability, or click **Auto-map** to let Boza place all of them at once.

The header reports how many applications are mapped, the share of tracked applications placed, and the share of placements that are validated — either confirmed by you or grounded in a trusted source.

***

## Refine, Rebuild, or Reset

| Action                | What it does                                                                                                                                                                                                             |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Refine your map**   | Takes one instruction in your own words, such as *Split Finance into Accounting and Treasury*, then **Apply change** applies only that. Everything else stays, and applications travel with the capabilities they sit on |
| **Rebuild structure** | Reopens the questionnaire and regenerates the structure. On the last step you can keep the groups and capabilities you added yourself                                                                                    |
| **Reset**             | Deletes the whole map — structure and every placement                                                                                                                                                                    |

{% hint style="warning" %}
A rebuilt structure always comes back with no applications on it, so you have to populate the map again. The placements you confirmed yourself are remembered and return on the next run. **Reset** removes everything and asks you to type a confirmation word first. Neither action can be undone from the interface, and your applications themselves are untouched.
{% endhint %}

***

## The Architecture Tab on an Application

Every approved application has an **Architecture** tab that connects it to the map:

1. **Features** — what your team uses the application for. Boza's AI suggests candidates; tick the ones you actually use, or add one the AI missed and choose the capability it belongs to.
2. **Business Capability** — the parts of your business the application supports. Ticking a feature places the application in the matching capability immediately. A dashed chip marks a suggestion, a solid one marks a placement your team confirmed, and the tooltip names the features behind it.
3. **Data & Infrastructure** — where the application runs, the company data it touches, and the tools it exchanges data with.

***

## Best Practices

* **Confirm the structure before populating.** Correcting a dozen capability names is far faster than re-placing a hundred applications.
* **Use Refine for small corrections.** It applies only what you ask; rebuilding starts the structure again.
* **Work the review queue rather than the whole map.** It surfaces the placements that are uncertain and business-critical first.
* **Tick features on the applications you know best.** Feature confirmations feed the map directly and improve later placements.
* **Clear the Unmapped column after adding applications.** New tools are not placed automatically; drag them onto a capability or use **Auto-map**.

***

## Related Guides

* [Applications](/docs/inventory/applications.md)
* [App Detail Page](/docs/inventory/applications/app-detail.md)
* [Data Inventory](/docs/inventory/data.md)
* [Infrastructure](/docs/inventory/infrastructure.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/platform/mapping.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.