> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/tenant-administration.md).

# Tenant Administration

**Tenant Administration** is where the platform administrators of a multi-tenant IZ Suite provision customer tenants, change them, and check that their background work is running.

Open it from **Administration** → **Tenant Administration** in the sidebar.

{% hint style="info" %}
Available only to platform administrators in the platform tenant.
{% endhint %}

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fllq6Kdjcx8x2LgijBYHl%2Fv2-ta-tenants.png?alt=media&amp;token=fddff6d7-0537-48f0-94a2-98356a6ffede" alt="Tenants screen with the Onboard Tenant, Global settings and Clear tenant cache buttons above the tenant directory"><figcaption><p>Tenant Administration</p></figcaption></figure>

## What a Tenant Is

A tenant is an isolated workspace inside one IZ Suite. Each tenant has its own:

* organizations, environments and applications;
* users, roles and access tokens;
* quality profiles, metric profiles, quality gates and schedules;
* global settings, sign-in options and email templates;
* licence, with its own licensed modules and allowances;
* notifications, audit records and dashboards.

Data never crosses tenants. A person signed in to one tenant cannot see or search another tenant's data, and reports, dashboards and MCP tools return only the data of the tenant the person belongs to.

### Sign-In Address

Each tenant has its own sign-in address. By default it is the tenant's **Slug** in front of the IZ Suite host, for example `https://acme.izsuite.example.com`. A tenant can also have an **External Link**: a host name of its own, such as `https://quality.acme.com`, that points at IZ Suite. IZ Suite picks the tenant from the address of every request, so the browser, single sign-on, access tokens, the CLI, IDE extensions and MCP clients must all use the tenant's own address. See [Tenants](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/tenant-administration/tenants.md#sign-in-addresses).

### Modules and Licence

Every tenant has its own licence key. The key decides which modules the tenant's users see and how many applications, scans or IDE keys they may use. A licence key can be applied to one tenant only. Tenant administrators see their licence in their own **Global Settings** → **Subscription**.

## The Platform Tenant

The platform tenant is the tenant that exists after installation and holds the platform operator's licence. Only its administrators see **Tenant Administration**, and only when the licence includes multi-tenancy. In the platform tenant the workspace products (Platform Analysis, Code Analysis, Dependency Insights) and Service Health are hidden; they are used inside customer tenants.

The platform tenant itself is listed in the tenant directory as **platform tenant**. It always stays **ACTIVE** and cannot be deleted, lose its organizations or have its managed settings changed.

{% hint style="warning" %}
You need a role that can manage tenants, in the platform tenant.
{% endhint %}

## Sections

| Section                                                                                                                                                | What it is for                                                                                                                                                                        |
| ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Tenants](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/tenant-administration/tenants.md)                   | The tenant directory: open a tenant to edit it, decide which settings you manage for it, delete its organizations or the tenant. Also **Global settings** and **Clear tenant cache**. |
| [Onboard a Tenant](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/tenant-administration/onboard-a-tenant.md) | Provision a new tenant with its first administrator, organization and licence.                                                                                                        |
| [Operations](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/tenant-administration/operations.md)             | Recorded activity per tenant and the most recent job runs across tenants.                                                                                                             |

## Platform-Wide Actions

Two actions on **Tenants** affect more than one tenant at a time:

* **Global settings** writes one value into the same setting of several tenants, for example a new AI model or API key for every tenant whose AI settings you manage. See [Tenants](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/tenant-administration/tenants.md#global-settings).
* **Clear tenant cache** makes every server look up again which tenant an address belongs to. Use it after you change a tenant's slug or external link. See [Tenants](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/tenant-administration/tenants.md#clear-tenant-cache).

## Next Steps

* [Onboard a Tenant](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/tenant-administration/onboard-a-tenant.md): create a tenant and hand it over to its administrator.
* [Tenants](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/tenant-administration/tenants.md): change a tenant, its sign-in address or the settings you manage for it.
* [Operations](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/tenant-administration/operations.md): find tenants whose background work is failing.


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/tenant-administration.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.
