Request
Signal Dispatch's service owner needs evidence that tenant-specific order reports can't read another tenant's rows. Create a nonowner reporting role, enable row security, set trusted tenant context and compare visible counts with owner-side audit totals. The browser setting demonstrates policy scope, not an authentication mechanism.
Data
Use the fictional customers, orders, items, event documents and account records supplied in the workspace. No production data is connected.
Final output
Complete all six checked stages and leave the final SQL and result available for review. Each stage names its required object or output.
Signal Dispatch's service owner needs evidence that tenant-specific order reports can't read another tenant's rows. Create a nonowner reporting role, enable row security, set trusted tenant context and compare visible counts with owner-side audit totals. The browser setting demonstrates policy scope, not an authentication mechanism.
Build the requested result in six checked stages. Each stage keeps the earlier SQL in the editor so you can extend the same work. The next stage begins with your own submitted script; Start over restores the reference starting point for that stage. Read the output contract before adding a column or changing a filter.
Keep source rows intact unless the task explicitly asks for a write. Missing values and period boundaries are included deliberately. The checker reruns the work against changed source records, so a fixed visible total isn't a valid substitute for the query or database object.
Grant only the local reporting operations needed by the audit.