What changes
- Organizations can invite a Dashboard viewer. The role reads the dashboards of the workspaces its teams are granted, and nothing else: no surveys, responses, contacts or feedback records.
- The permission schema (
authzed/schema.zed) changes. It adds theorganization#dashboard_viewerrelation and adashboard_readpermission on workspaces and Feedback Dataset assignments. team#managenow needs a product membership (owner, manager or member). A billing member who is a team admin can no longer rename the team or change its members; an owner or manager can.- A data migration adds
dashboard_viewerto the organization role values. No existing member changes role. - The role needs both the Access Control and the Dashboards entitlements. If either lapses, viewers keep the role and see a “not available on this plan” page instead of the dashboards.
Before you upgrade
Upgrade
Follow the runbook for your setup: Kubernetes, Docker Compose or one-click. Run permission preparation with the schema digest. It applies the new schema and reconciles the relationships before the new version starts. On one-click,./formbricks.sh update checks the permission setup and stops with a schema drift (exit 2) if
preparation hasn’t run. Nothing has been stopped or migrated at that point: run the preparation step, then run
the update again.
Don’t invite anyone as a Dashboard viewer until the upgrade is done and its checks pass. Owners, managers and
members don’t depend on the new relation, so they work as before.
What changes for API and MCP clients
- MCP
get_chart_datagains an optionaldashboardIdandpicks. Without them it reads the saved chart as before and still needsdashboards:readandfeedbackRecords:read. WithdashboardIdit reads the chart as that dashboard shows it, with dashboard filters applied. That also needs both scopes, except for a Dashboard viewer’s client, which holds onlydashboards:read. Its result adds an optionalunfilterableFilters. Existing clients keep working. GET /api/v3/charts/{chartId}/data: a date range replaces the range saved on the chart’scollectedAttime dimension, as a dashboard’s date range does. A range the author saved as acollectedAtfilter rule still narrows the result. This endpoint is new in 6.2.- Organization roles in API responses:
GET /api/v2/organizations/{organizationId}/usersreturnsdashboard_vieweras a user’sroleonce someone holds it. A client that validates roles against a fixed list must accept it.GET /api/v2/rolesdoesn’t list it, and the v2 user create and update refuse to give it (403): the role is given in the app. The v1 API returns no organization roles.
If something goes wrong
The 6.1 schema has nodashboard_viewer relation, and the 6.1 app doesn’t know the role. Before you go back to
6.1, give every Dashboard viewer another role, such as Member, in Organization settings → Members. Then
restore your 6.1 backup as described in backup and restore. If you
restore only the 6.1 schema rather than the whole backup, run formbricks-authzed backfill --apply afterwards.