From 38ecb2e1a0322ed1ccfb93087fca1622c006bd8e Mon Sep 17 00:00:00 2001 From: rcourtman Date: Tue, 21 Jul 2026 18:35:32 +0100 Subject: [PATCH] Document how the Enterprise multi-tenant license is obtained The requirements table named an Enterprise license but the pricing page only sells Community, Relay, and Pro, leaving no visible path to the capability. A Pro buyer purchased today expecting multi-org on the strength of this doc. State plainly that the self-serve tiers do not include the capability and where to ask for Enterprise licensing. Contract-Neutral: docs-only: state how the Enterprise multi_tenant license is obtained; no runtime change --- docs/MULTI_TENANT.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/MULTI_TENANT.md b/docs/MULTI_TENANT.md index dbb9293af..a16cd1e18 100644 --- a/docs/MULTI_TENANT.md +++ b/docs/MULTI_TENANT.md @@ -13,6 +13,8 @@ This is not the canonical Pulse MSP model for separate customer businesses. MSP Without these, all API calls return `501 Not Implemented` (flag off) or `402 Payment Required` (no license). The **default** organization always works regardless. +The Community, Relay, and Pro tiers do not include the `multi_tenant` capability, and Enterprise licensing is not sold self-serve on the pricing page. Email [support@pulserelay.pro](mailto:support@pulserelay.pro) to arrange an Enterprise license. + ## Quick Start 1. Set `PULSE_MULTI_TENANT_ENABLED=true` in your environment and restart Pulse.