Survey Limits
Two current plan limits control how many surveys your organization can have. Both are actively enforced. A third numeric limit for immutable version history is approved but is not yet present or enforced.
Maximum total surveys
What it controls: the total number of surveys your organization can have at one time.
- Who it affects: anyone who creates surveys for your tenant.
- When it applies: when a new survey is being created.
- What happens when reached: creating another survey is blocked with a clear message; your existing surveys are unaffected.
- Data: existing surveys are never deleted. If the limit is lowered below your current count, you simply cannot create new surveys until you are back under it or the limit is raised.
Maximum active surveys
What it controls: how many surveys can be active (published / collecting responses) at the same time.
- Who it affects: anyone who activates or publishes a survey.
- When it applies: when a survey is being activated or published. The survey you are currently activating is not double-counted.
- What happens when reached: activating another survey is blocked; surveys that are already active stay active.
- Deactivating is always allowed. To make room, deactivate a survey you no longer need to keep collecting on, then activate the new one.
How to see your usage
- Tenant admins can review survey counts on the dashboard overview and plan/usage pages.
- Platform admins can view and adjust these limits per plan or per tenant.
Planned survey-version history limit
MaxSurveyVersionsPerSurvey is approved for implementation planning. It will use 0 to disable the customer-visible Version History/Restore surface and 1..50 to allow that many visible/restorable versions per survey, including the current version. It will not support -1 or unlimited. Disabling or lowering it will hide older history without deleting snapshots or changing responses, and increasing it later will re-expose the newest retained versions within the new value.
This limit, Version History, Restore, immutable response-version links, and runtime contentHash are not implemented today. When implemented, contentHash and full runtime refresh will remain available to every tenant even at value 0.
Special values
- The current survey guards enforce only positive
MaxSurveysandMaxActiveSurveysvalues. Missing,0, and-1values do not impose a cap in these guards. - Catalog-backed plans should use explicit positive quotas when survey capacity must be enforced.