Manage Tenant Overrides — Platform Admin

Overview

Tenant-specific entitlement changes serve the business purpose historically called “tenant overrides”: granting one tenant different limits without changing the plan catalog for everyone. Current source contains no separate tenant-override entity or general override mutation service. The supported representation is a plan-change or limit-increase order whose Applied state updates the tenant subscription and freezes its entitlement snapshot.

When to Use Overrides

Use overrides when:

• A tenant needs more users, storage, or surveys than their current plan allows, but upgrading to a higher plan is not yet appropriate.
• A tenant is in a trial or evaluation period and needs extended limits.
• A tenant has submitted a limit increase request that has been approved.
• A temporary campaign or project requires a short-term limit increase.

Viewing Overrides for a Tenant

1. Open the tenant's authorized subscription/commercial details.
2. Select or inspect the tenant through the explicit selected-tenant and subscription controls.
3. Compare frozen TenantSubscriptionEntitlement values with the current plan catalog when investigating a tenant-specific difference.

The permission/catalog label Tenant Overrides remains for compatibility, but source verification found no dedicated controller/model implementing the older dropdown workflow.

Adding an Override

The following procedure preserves the business intent. Do not look for an unsupported Add Override button; use a tenant-owned commercial limit-increase or plan-change order:

1. Select the tenant and create the appropriate commercial order.
2. Choose a limit from the active catalog.
3. Common limit types include:
   • Maximum users
   • Maximum storage
   • Maximum surveys
   • Tenant response capacity for the configured usage period
   • Maximum integration API clients
4. Enter a value within catalog bounds and no lower than the included value. Boolean capabilities accept only 0 or 1.
5. Review the server-authoritative effective-dated price. The current snapshot model has no generic override-expiry field or automatic-reversion promise.
6. Submit, approve, complete payment/proof when applicable, and Apply the order. Only Applied updates the entitlement snapshot.

Removing an Override

The current source has no direct Remove Override mutation. To reduce a tenant-specific entitlement:

1. Inspect current entitlement and usage so a reduction does not conflict with live resources.
2. Create and review the appropriate plan-change order.
3. Apply it only after commercial and operational approval.

No silent immediate reversion occurs. PlanResolver reads the frozen snapshot until an Applied order intentionally replaces it; editing the catalog alone does not alter the tenant.

Override vs. Plan Change

• Tenant-specific entitlement change: Applies to one subscription snapshot only and does not affect other tenants on the catalog plan.
• Plan change: Moves the tenant to a different plan with different base limits. Affects billing.

Use overrides for exceptions. Use plan changes for permanent upgrades or downgrades.

Audit Trail

Commercial order transitions and entitlement application retain persisted actor/time and audit information. Because no dedicated override mutation exists, do not claim a separate override-add/remove audit event. Review the order, subscription entitlement rows, and applicable audit records together.

The current catalog has 17 active keys in six groups. Four are Boolean 0/1 capabilities, with no parallel PlanFeature entitlement model. Prices are effective-dated while Applied entitlements are frozen, preventing silent retroactive changes.