---
title: Tenants
description: The tenant directory at
---

# Tenants



## Purpose

TENANTS is the directory and the console's selection driver: the tenant row you click here scopes PIPELINE, CAMERAS, LOGS, and AGENTS. It is also where remote support is armed and disarmed.

Deep link: `ops.useargus.co/#/tenants` (nav group MONITOR). This is the default view when the console opens with no hash.

## What it shows

A header count reading `TENANTS (N · M armed)`, then a table with one row per remote-support tenant:

* TENANT: the human-readable org name with the tenant id as a dim subtitle (id alone when no name is on record).
* REMOTE SUPPORT: armed or not armed (armed means consent is on record).
* AGENTS: active and total enrolled agent counts.
* LAST ACTIVITY: relative time, for example "5m ago".
* ACTION: an ARM or DISARM button reflecting the current state.

## Actions

* Click any row to select that tenant. The selection persists and the console opens its [Agents](/docs/console/agents) view.
* ARM opens a step-up modal: type the tenant id to confirm, enter a reason (at least 3 characters), a consent document id (prefilled), and check "I confirm tenant consent was obtained". Submit button label: ARM.
* DISARM opens the same modal without the consent fields and warns "This ends any LIVE remote-support session for this tenant." Submit button label: DISARM.
* On a 429 rate limit the submit button disables and shows a retry countdown.

On success the modal closes, a toast confirms, and only that tenant's row is patched in place.

## Matching CLI

```bash
argusctl tenant ls
argusctl tenant show <tenant>
argusctl tenant arm <tenant> --reason "ride-along"
argusctl tenant disarm <tenant> --reason "done"
```

See [argusctl tenant](/docs/cli/tenant) and the [arm and disarm guide](/docs/remote-support/arm-disarm).

## Notes

* Polled on the 15 second timer; rows are patched cell by cell, so row-click and button listeners survive ticks.
* The directory payload is mirrored to localStorage, so on reload the panel paints instantly from the last-known data and then revalidates within a few seconds. A tenant added, removed, or armed since the last load can read stale for that brief window.
* Empty state: "No tenants in the remote-support registry yet."
* Arm and disarm require a PAT with the `remote_support:arm` scope and are per-operator rate limited.


---

For a semantic overview of all documentation, see [/sitemap.md](/sitemap.md)

For an index of all available documentation, see [/llms.txt](/llms.txt)

For agent-facing discovery, including API and MCP surfaces, see [/agents.md](/agents.md)