Share Pages publicly
Public access lets anyone with a link read the Workspace’s Pages without signing in or joining the Workspace. It is off for every new Workspace, and only a Workspace Owner can turn it on or off.
What becomes public
Section titled “What becomes public”Public access applies to the whole Workspace, not to one Page or folder:
- Every Page in the Workspace, now and in the future.
- Past and future results of dashboards added to Pages.
- Uploaded documents and their replacements.
While it is on, anyone with the Explorer role or higher can publish by adding to Pages. Check what is in Pages, and who can add to it, before you turn it on.
Turn public access on or off
Section titled “Turn public access on or off”- Open Settings in the Workspace sidebar, then Public access. The section shows whether Public Pages is on or off.
- Turn the Public Pages switch on. Review the confirmation, Make all Pages in your Workspace public?, and select Make public.
- Open a Page in a private browser window to check what a visitor sees. Pages shows Anyone with a link can view them. while access is on.
To stop public access, turn the switch off. This stops new public access; downloads and link previews that were already shared may remain.
Organization Admins who are not Workspace Owners can see the setting but not change it. Agents can’t change it either.
What visitors can do
Section titled “What visitors can do”Visitors can read the Page tree, Pages, current documents, and the results of dashboards added to Pages. They can change a dashboard’s input controls, which runs its queries; a signed-in visitor who isn’t a member is recorded as the person who asked, and other visitors appear as Public reader in Recent activity.
Visitors can’t edit anything, start new dashboard results, refresh or cancel runs, or read earlier document versions. They can download a document’s original file only when it can’t be displayed safely. SQL text, Connector details, and internal IDs are never shown to them. Widgets displaying SQL results show an SQL badge based on the query types recorded for those results. Before results are ready, the badge uses the dashboard definition’s query types. Visitors cannot open Show SQL. Agents always need direct Workspace membership, even when public access is on.
SQL dashboards and public inputs
Section titled “SQL dashboards and public inputs”A dashboard added to Pages can contain saved SQL queries. Visitors changing its inputs execute those queries with the Connector account’s warehouse permissions. SQL can reach tables that are not selected in Catalog, and result column names may expose the author’s physical-source aliases.
Use a dedicated read-only warehouse account whose grants permit only the data that may become public. Monomer’s native SQL check catches common accidents and does not guarantee read-only execution. Excessive procedure, pass-through, or remote/external function privileges can allow side effects to repeat whenever visitors change inputs or schedules run. Binding inputs as typed values does not protect SQL that hands those values to warehouse dynamic-SQL functions or procedures; authors must keep reader-controlled inputs out of those paths.
Before you share a link
Section titled “Before you share a link”- Use a warehouse account that can read only data that may become public through these dashboards; see Security.
- Tell Explorers in the Workspace that what they add to Pages becomes public.
- Use Copy link on a Page to share it. See Share work in Pages.