Dashboard Viewer Data Check

How to use Dashboard Viewer Data Check

A dashboard screenshot that looks right is not evidence that every viewer sees only intended rows. Reconcile stable viewer and row IDs before running real authorization tests.

1. Declare every expected viewer with a known complete listed scope, a known empty scope or an explicitly unknown scope.
2. Enter authorized neutral row entitlements and rows actually observed in that viewer’s fixture.
3. Resolve unexpected and missing rows, then run real authenticated access and export tests against the deployed dashboard.

Good to know

• This compares supplied IDs only. It does not log in, query a dashboard, test row-level security, detect other leaking columns, inspect exports or prove that no other rows can be accessed.
• Unknown is not treated as an empty approved allowlist. Known listed scopes require at least one row and empty/unknown scopes must not contain a partial entitlement list. Any unknown or mismatch holds release within the entered fixture.
• Each input field is limited to 8,000 UTF-16 characters. CSV needs the exact displayed header and at most 100 data rows. Quoted commas, doubled quotes and quoted newlines are supported. Duplicate identities are refused unless the tool explicitly reports them as findings.
• Markdown and CSV are editable review artifacts, not certificates. Spreadsheet-like text is apostrophe-prefixed in CSV to reduce formula execution risk; check the actual importer before sharing. Decimal ratios are rounded to at most 12 places.
• Runs only on the records you enter, locally in your browser. No AI call, provider connection, account inspection, upload, automatic outreach or saved input. Use neutral identifiers rather than personal or secret content.