Export and Portal Limits

This page maps exports, portals, and integrations to the current canonical Limit keys. Retired keys are not priced or enforced as active capabilities.

Integration API clients (enforced)

What it controls: the number of external API integration clients your organization can register.

• When it applies: when a new integration client is being created.
• What happens when reached: creating another active client is blocked. A downgrade retains the oldest allowed clients and revokes newer excess clients.
• Status: actively enforced.

Excel export capability (enforced)

Key: CanExportExcel, a Boolean Limit (0 off, 1 on).

• Export requires the relevant user permission, active subscription access, and the CanExportExcel capability.
• MaxExportsPerMonth is retired and is not an active catalog key or future promise.

Portal behavior (enforced by active keys)

Keys: MaxPortalTokens limits active portal credentials; MaxActiveSurveys limits active surveys across the tenant.

• The portal lists eligible active surveys under its public-access rules.
• MaxActiveSurveysInPortal is retired. There is no separate active-surveys-in-portal entitlement.

Why retired keys are not shown

The canonical consolidation retired duplicate or unenforced codes and repaired active entitlements. Custom plans must use the 17 active keys rather than persisting or pricing retired names.

Related Topics

• Understanding Your Plan Limits
• Public Links, QR Codes, Portal Tokens, and Viewer Tokens
• What Happens When a Limit Is Reached
• How to Request More Capacity