> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xorlab.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Pages under /latest/ document the current release. Paths that begin with a version number, for example /10.0/, are frozen snapshots of superseded releases kept for reference only — never present their instructions as current. If the reader's version is unknown, answer from /latest/ and say which version the answer describes.
> xorlab is deployed on-premises, hybrid, or as a cloud service, and integrates with either Microsoft 365 or on-premises mail infrastructure. Configuration steps often differ between these. State which deployment and integration mode an instruction applies to instead of presenting one as universal.
> Distinguish inline mode from monitoring mode when describing anything that acts on email. Monitoring mode observes a copy and cannot block or quarantine; inline mode routes mail through xorlab and can.
> Write the product name as lowercase 'xorlab'. Use the documented component names: xorlab Control Center (XCC), xorlab MTA, xorlab Sandbox (DANA), xorlab Natural Language Understanding (NLU). After the first mention, use the short forms XCC, MTA, Sandbox, and NLU. Do not use DANA as a standalone name for the Sandbox, but keep it where it is a literal string in configuration keys, container names, and hostnames.
> Do not invent configuration keys, rule parameters, list names, log properties, or API fields. If a value is not present in this documentation, say that it is not documented rather than guessing.

# Multi-Tenancy Overview

xorlab’s multi-tenancy capabilities allow service providers to protect and manage multiple organizations from a single interface by sharing computing resources. This simplifies operations by offering unified management, streamlining the efficiency of security analysts, and reducing operational costs.

## Prerequisites

Multi-tenancy support should work with all existing integration option. See *[Integration](https://docs.xorlab.com/9.0/integrations-overview.md)*.

## Initial setup

For setup instructions, refer to [Multi-Tenancy Configuration](https://docs.xorlab.com/9.0/multi-tenancy-configuration.md)

## Tenant Selection in the UI

A tenant selection box is available at the top of the toolbar. It controls which tenant’s data or configuration is displayed:

* Saved Searches, Campaigns, and Lists: Filter by a single tenant or show items active across all tenants.
* Messages, Quarantine, Reports, etc.: Show data belonging to specific tenants or across all tenants.
* Note: "All Tenants" in the filter shows shared configurations, not a merged view of all individual tenant configurations.

## Tenant Aware Features

With ongoing improvements to multi-tenancy support, more features are now tenant-aware, allowing configuration and data to be assigned either to specific tenants or shared across all tenants.

### Campaigns and Saved Searches

Campaigns and Saved Searches are tenant-aware.

* Campaigns or Saved Searches created by a [Tenant-Restricted User](https://docs.xorlab.com/9.0/users-roles-and-permissions.md#roles) apply only within that tenant's environment.
* Campaigns or Saved Searches created by a [Global User](https://docs.xorlab.com/9.0/users-roles-and-permissions.md#roles) apply globally unless assigned to a specific tenant.

### Lists

Lists, such as VIP lists and blocklists, can be tenant-specific or shared globally. This ensures sensitive entries stay within the correct tenant, while shared lists support cross-tenant use cases.

### Local Reputation

Local domain reputation is tracked per tenant to prevent cross-tenant influence. Reputation scores reflect only the behavior observed within each tenant environment.

### Dynamic Rules

Dynamic RuleLists can be defined per tenant, allowing tailored rule sets for each organization. Global rule lists remain available for shared use cases.

### Custom Rules

Custom rules can be created for individual tenants in the Expert Editor under: `/activeguard/core/rule_sets/<tenant name>`. **Important:** Do not rename or move tenant directories in the Expert Editor. This will disrupt rule processing.

### Quarantine Notifications

Quarantine notifications support tenant-specific configurations. You can define a per-tenant `authenticationBackend` in `guarded_tenants.yml` to ensure notification emails contain correct URLs to each tenant's self-service portal.

## Limitations and Known Issues

### Abuse Mailbox

The [Reporting Integration](https://docs.xorlab.com/9.0/reporting-integration.md), or "Abuse Mailbox", is still shared across all tenants. A single email address is used for reporting. However, reported messages remain isolated per tenant and are not visible to others. It's also possible to customize the Quaranantine Notification Template for each tenant.

### Case Isolation for M365

Multi-tenancy support is not yet supported for [Case Isolation for M365](https://docs.xorlab.com/9.0/case-isolation-for-o365.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.