Control who can see a report page
Keep native or HTML pages invisible to viewers while preserving editor access and protected history.
Limit a page to editors and the people added to it to keep it available to report editors while excluding it from the report's viewer-facing content. This guide calls such a page invisible. The setting applies to both native and HTML pages.
Use it for work in progress or supporting pages that editors need. It is an access control for page content, separate from presentation mode or a collapsed navigation panel.
Change page visibility
- Open the report as an Owner or Admin.
- Find the page in the page list.
- Use its visibility control: a lock icon labeled Limited to editors and people added to the page (invisible), or Open to everyone with access to the report (visible).
- Wait for the change to save.
- Review the report using the intended viewer permissions.
The control updates its indicator during the save and reports a failed change. Editors can see the invisible indicator, but cannot change visibility unless they have Admin or Owner access.
Who can see the page
| Report role | Open to everyone | Limited (invisible) | Change visibility |
|---|---|---|---|
| View | Yes | No | No |
| Edit content | Yes (like View) | No (unless added to that page) | No |
| Edit | Yes | Yes, with an indicator | No |
| Admin | Yes | Yes | Yes |
| Owner | Yes | Yes | Yes |
A team management role does not bypass this table. The person's effective report permission determines the result.
What invisibility protects
Viewer-facing access excludes the invisible page from page lists and report catalogue content. Protected reads also cover its visual metadata, results, relevant history, and AI context.
Knowing the page's URL or identifier is not permission to open it. The server checks authorization rather than relying only on a hidden navigation item.
Organization membership, an API key, and a copied report link also do not bypass visibility.
Conversations and history
Viewers can chat in a report that has invisible pages. Chats are private to the account that created them, so a viewer's conversation holds only what that viewer's own runs were shown. The assistant's page tools leave invisible pages out of every result for a viewer. When a message names a page or visual, for example through the current selection, Unity checks it and leaves an invisible page out of the assistant's context.
Saved authoring history needs Edit access: change snapshots, HTML revisions, and restore. A snapshot or revision can contain an invisible or deleted page.
Duplicate, delete, and restore
Duplicating an invisible page preserves its invisibility. Deleting a page and bringing it back from Version history keeps its visibility: a restore never resets access.
HTML page version restoration keeps current access settings. It restores supported content and registrations, not a historical viewer policy.
Use Version history to understand content restoration separately.
Access changes in an open report
Unity rechecks access as the workspace regains focus, receives access-change signals, and periodically while visible. Server operations also check current permissions.
An open page may therefore disappear or stop accepting actions after an access change. The recheck does not recall information already delivered to a browser.
Visibility and data security
Page visibility protects access to that page. It is not source-level row security and does not prevent an authorized editor from using a shared connection through other permitted workflows.
If different users must receive different source rows, enforce the relevant source and application access requirements in addition to page visibility. A display filter is not a security boundary.
Troubleshoot visibility
| Problem | Check |
|---|---|
| Viewer cannot find a page | Whether it is marked invisible and whether report access remains valid. |
| Editor can still open an invisible page | Expected behavior for Edit, Admin, and Owner. |
| Editor cannot toggle the flag | Visibility changes require Admin or Owner. |
| A viewer cannot open Version history | Version history needs Edit access to the report or the page. |
| A copied page remains invisible | Duplication preserves visibility intentionally. |
See Sharing and access for effective report roles.
Questions about your environment? Contact us.