> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/intercom/configuration/set-up-and-configure-tenants.md).

# Set up and Configure Tenants

Create tenants and understand how they consume licenses

Create a tenant in Verkada Command and add it to a Verkada Intercom so visitors can call that occupant from the directory. A tenant is an occupant of part of a building or space, such as a suite or business. On an intercom, a tenant is one line in the directory, or the button a visitor presses to call that occupant and enter the building.

A tenant exists independently, separate from any one intercom. You can reuse the same tenant on multiple intercoms, at one site or across sites, without re-creating its call flow.

{% hint style="warning" %}
Tenants apply only to the Verkada TS12-N-R2B, TD63, and TK74 when multitenant mode is turned on.
{% endhint %}

***

## Create a tenant

{% hint style="warning" %}
Tenants are created on the Tenants page, not on each intercom’s directory.
{% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Intercom > Tenants.**
{% endstep %}

{% step %}
**Click Create tenant.**
{% endstep %}

{% step %}
**Enter the required information.**

* **Tenant name**
* **Site(s)**—You can add a tenant to more than one site. Each site consumes one license
  {% endstep %}

{% step %}
**(Optional) Enter any additional tenant information.**

<table><thead><tr><th width="240.92578125">Field</th><th>Description</th></tr></thead><tbody><tr><td>Logo</td><td>An image that represents the tenant. Displayed on the TK74 only.</td></tr><tr><td>Display name</td><td>The name shown in the directory on the TK74.</td></tr><tr><td>Unit</td><td>The tenant’s unit or suite number. Currently used as an internal reference only.</td></tr><tr><td>Call Code</td><td>The code a visitor enters to dial the tenant on a TD63 or TK74. A call code is <em>required</em> to add a tenant to a TD63.</td></tr><tr><td>Start and End Date</td><td>The dates on which the tenant’s lease begins and ends. If filled out, these dates automatically change the tenant's <em>status</em>. (See row below)</td></tr><tr><td>Status</td><td>Whether the tenant is active or inactive. Only active tenants consume a license and can be called on an intercom. </td></tr><tr><td>Notes</td><td>Additional information about the tenant. Information contained in this section can be used as context for an <a href="https://help.verkada.com/intercom/configuration/create-and-manage-ai-receivers.md">AI Voice Directory</a>. </td></tr><tr><td>Call Flow</td><td>Each tenant has a single call flow, which applies to every intercom that lists that tenant. Refer to <a href="https://help.verkada.com/intercom/configuration/add-and-configure-receivers-in-intercom/create-and-use-shared-call-flows.md">Create a call flow</a> for instructions on how to configure call flows. </td></tr></tbody></table>
{% endstep %}

{% step %}
**Click Save.**
{% endstep %}
{% endstepper %}

***

## Add a tenant to an intercom

{% hint style="warning" %}
A tenant must belong to the same site as the intercom.
{% endhint %}

{% hint style="info" %}
Only active tenants appear in the directory and can be called. You can add an inactive tenant to an intercom before activating it.
{% endhint %}

Add a tenant from the **Tenants** page or from the intercom **Receivers** tab.

{% tabs %}
{% tab title="Tenants page" %}
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Intercom > Tenants.**
{% endstep %}

{% step %}
**Select the tenant to open the details panel.**
{% endstep %}

{% step %}
**Under Intercoms, click Edit intercoms.**
{% endstep %}

{% step %}
**Select the intercoms where this tenant should appear.**
{% endstep %}
{% endstepper %}
{% endtab %}

{% tab title="Receivers tab" %}
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Intercom.**
{% endstep %}

{% step %}
**Select the intercom.**
{% endstep %}

{% step %}
**Click Receivers.**
{% endstep %}

{% step %}
**Click Add tenants.**
{% endstep %}

{% step %}
**Select the tenants to add to this intercom.**
{% endstep %}
{% endstepper %}
{% endtab %}
{% endtabs %}

***

## How tenant licensing works

Each tenant must be assigned to a site. Each combination of a tenant and a site consumes one LIC-ITT license. A tenant that appears on more than one intercom at the same site still counts as one combination.

* LIC-ITT licenses are sold in bundles of 10 tenants.
* Inactive tenants do not consume a license.

#### Review a licensing example

* **Suite 100** is assigned to two sites, so it consumes two licenses.
* **Suite 200** is assigned to one site, so it consumes one license.
* **Suite 300** appears on two intercoms at the same site. That is one tenant-site combination, so it consumes one license.

<table><thead><tr><th>Tenant</th><th>Assigned Site</th><th>Intercoms</th><th data-type="number">Licenses Consumed</th></tr></thead><tbody><tr><td>Suite 100</td><td>Site A</td><td>Lobby</td><td>1</td></tr><tr><td>Suite 100</td><td>Site B</td><td>Main Entrance</td><td>1</td></tr><tr><td>Suite 200</td><td>Site A</td><td>Lobby</td><td>1</td></tr><tr><td>Suite 300</td><td>Site A</td><td>Lobby, Parking Garage</td><td>1</td></tr></tbody></table>


---

# 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://help.verkada.com/intercom/configuration/set-up-and-configure-tenants.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.
