Overview
Boards are great for internal use, but most clients and stakeholders don't have TagPipes logins and shouldn't need one. Reports solve that. A Report wraps one or more boards in a public URL you can share with anyone. Viewers see a polished dashboard view with a dark theme; they don't see the Lens admin UI or anything else behind the login wall.
Reports are live. When the underlying tables sync new data, the report updates the next time someone loads the URL. You don't export or snapshot anything, which means the client always sees the latest numbers without you pushing an update.
Navigate to Reports
Open Lens > Reports from the left sidebar. The list shows every report for your property along with its board count, creation date, and access mode (public or password-protected). Click Add Report to create a new one.
Configure the report
Give the report a name. This is what you'll see in the admin list, and if you turn on password protection it also appears on the password prompt. Pick the boards you want included; a report can contain one board or many, and each board becomes a section in the rendered output.
Think about ordering. The boards appear in the report in the order you add them, which becomes the top-to-bottom scroll sequence for viewers. Lead with headline numbers, follow with breakdowns, and save long-tail detail tables for last.
Set access controls
By default, a report is public. Anyone with the link can view it. If you need to restrict access, set a password on the report. Passwords are hashed and the viewer's authenticated session expires after 30 days, at which point they'll need to re-enter the password.
Public reports are suitable for most client work. Password protection is useful when the data is sensitive or when you want some deterrent against casual link sharing. Remember that password protection isn't a security boundary on its own; if the link and the password both leak, anyone with both can see the data.
Publish and share
Click Save to publish. Lens generates a unique URL in the format /r/<token>. Copy that URL and send it to whoever needs to see the report. There's no setup on the viewer's side: they open the link, optionally enter the password, and the dashboard loads.
Reports use a dark premium theme by default, which suits client presentations. Rate limiting is applied per token (60 requests per minute) so a leaked URL can't be abused for scraping. Table IDs are validated against the tiles on the included boards, which means viewers can't craft a request to read data from tables you didn't intend to expose.
Troubleshooting
Report shows "Access Denied" or 404
Confirm the URL is exact. Report tokens are long random strings and one wrong character breaks the match. If the URL is correct, the report may have been deleted or the property's access settings may restrict public exposure. Check the Reports list in the admin UI to verify it still exists.
Tiles load on some boards but not others
A board tile needs the underlying table to have data and to be accessible. If one table hasn't synced recently or the sync failed, the tile shows empty while neighboring tiles on healthy tables render fine. Check the Tables list for recent sync failures and re-run the sync.
Viewer sees "rate limit exceeded"
Reports cap traffic at 60 requests per minute per token to prevent abuse. If a client hits that limit under normal use, they may be hammering the refresh button or have the report embedded somewhere that polls. If the use case is legitimate, contact support to discuss a higher limit.