> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/integrations/software-management/torii.md).

# Torii

Optimize SaaS spend and automate license management with Torii intelligent platform

Torii is a SaaS management platform that provides visibility, optimization, and automation for your entire SaaS stack. Connecting Torii to Harmony enables intelligent license management, automated provisioning workflows, and data-driven SaaS optimization to reduce costs and improve security.

### What the Torii integration enables

| Capability           | Description                                              |
| -------------------- | -------------------------------------------------------- |
| License Optimization | Track and optimize SaaS licenses across all applications |
| Usage Analytics      | Track application usage to identify unused licenses      |

### Prerequisites

* **Torii Administrator Access**: Admin role in Torii
* **Torii Subscription**: Active Torii account with connected SaaS applications
* **Harmony Account**: Active Harmony workspace

### Connect Torii to Harmony

#### Step 1: Generate API Token in Torii

1. Log in to Torii at `https://app.toriihq.com`
2. Go to **Settings** > **API Access**
3. Click **Generate API Key**
4. Under **Choose type**, select **Torii API**, and enter a description (e.g. `Harmony Integration`)
5. Generate the key and copy it - Torii shows the key only once

#### Step 2: Navigate to Integrations

1. Log in to your Harmony dashboard
2. Go to **Settings** > **Integrations**
3. Find **Torii** under **Software Management** (or search for it by name) and click its card

#### Step 3: Enter API Credentials

1. Enter your Torii API key in **API Key**
2. Click **Connect**

### What Harmony syncs

**From Torii:**

* All discovered SaaS applications
* License counts and user assignments
* Application usage statistics
* SaaS spending and cost data
* Contract details and renewal dates
* Shadow IT discoveries

### Use cases

<details>

<summary>Automated License Lifecycle</summary>

Provision the right SaaS licenses on hire and automatically reclaim all licenses when an employee exits

</details>

<details>

<summary>Cost Optimization</summary>

Identify inactive licenses, notify users, and auto-revoke after a grace period to reduce SaaS spend

</details>

<details>

<summary>Shadow IT Governance</summary>

Detect unsanctioned app usage, assess risk, and guide employees to approved alternatives

</details>

<details>

<summary>Just-in-Time Provisioning</summary>

Grant temporary SaaS access for a defined period and automatically revoke it when the time expires

</details>


---

# 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.harmony.io/integrations/software-management/torii.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.