Skip to main content
Survey visibility is part of the Enterprise Edition. On Formbricks Cloud it comes with plans that include access control.

Two options

New surveys start Restricted (on a self-hosted instance, once an admin turns visibility on). Respondents are never affected: a restricted survey still works through its link, your website or your app.

Change visibility

  • When activating: Formbricks asks Who can view this survey in your workspace? before it is activated.
  • Anytime: open Collaborate from the survey’s row menu or the editor.
Only the author and organization owners or managers can change it.

Restricting a survey

Formbricks shows how many colleagues lose access and asks you to confirm.
A survey connected to an integration, webhook, workflow or feedback source can’t be restricted. Disconnect those first — Formbricks lists them for you.
Restricting stops new responses from reaching feedback sources, but it doesn’t remove what they already imported. Feedback records created from the survey before you restricted it stay in place, and dashboards built on them keep showing them.

If the author leaves

Their restricted surveys stay restricted. Owners and managers can still open them and make them visible to the workspace.

Turn it on when self-hosting

After upgrading to 6.1, a self-hosted instance keeps every survey visible to the workspace and hides the visibility controls until an admin turns them on. You do this once. From then on, new surveys start Restricted, so let your team know before you switch it on. Docker and one-click:
Kubernetes, from a running Formbricks pod:
The command copies every survey’s owner and visibility into SpiceDB, checks the result twice, and only turns visibility on when both checks are clean. To go back to workspace permissions, for example while repairing SpiceDB, run the same command with --clear-ready instead of --apply --mark-ready. That stops new visibility changes; surveys that are already restricted stay restricted. Details are in SpiceDB operations.