Skip to content
Monomer

Share work in Pages

← Dashboards & Pages

Pages is where your team shares finished work: dashboards and documents, organized in folders. Every Workspace member can read Pages, including Viewers, who see the Workspace only through Pages. Adding, uploading, and organizing need the Explorer role or higher.

A folder does not restrict who can read what is in it. Confirm that the content is appropriate for the whole Workspace before you add it. When public access is on, anyone with a link can read Pages; see Share Pages publicly.

Add a dashboard

Section titled “Add a dashboard”

A dashboard Page links to an existing dashboard. Readers of the Page can read the dashboard’s past and future results and change the dashboard’s own input controls; they can’t change its definition.

  1. Select Pages in the sidebar, then open the destination folder. For the top level, open Search and choose Pages under Go to.
  2. Select Add dashboard. Search for and choose the dashboard.
  3. Check Name in Pages and Destination, then select Add to Pages. The new Page opens.

The Page has its own name; renaming the dashboard does not rename its Pages. Remove from Pages removes only the selected Page and keeps the dashboard, its results, and other linked Pages. From a dashboard Page, Explorers and higher can choose Open dashboard to work with the dashboard directly.

Deleting the dashboard removes all of its linked Pages along with its draft, results, and schedules, and cancels running queries. Public readers lose access to those Pages too. Restoring the dashboard keeps its original dashboard ID but does not restore Pages or past results; add a new Page to share it again.

Read dashboard results with an agent

Section titled “Read dashboard results with an agent”

Read the dashboard Page and follow its advertised sessions LIST operation. Choose an existing Session and read its path. Page readers are offered resolve for existing Sessions; they cannot open a new Session, change its fixed Parameters, or force a refresh of successful results through the Page.

Describe the Session’s advertised resolve entry with monomer_describe, then invoke it with kind: DASHBOARD_SESSION_RESOLVE and complete variables. Copy the Page Session body’s initialVariables for initial results, or send all of your selected Variable values after an input change. Include every declared name and explicit null for nullable values. {} is valid only when the Session declares no Variables; it does not apply defaults or retain earlier values.

Resolve checks current Page access and its Dashboard connection. For each named query it reuses the latest matching SUCCEEDED run within the same Session, otherwise joins a matching RUNNING run, otherwise starts a new run. It does not create a Session or store your result selection. The ACCEPTED response returns a PAGE_SESSION result.path, validated variables, and a complete queryRuns map of Page QueryRun paths. Read each path, observe RUNNING until completion, then follow its advertised result READ when SUCCEEDED. A SUCCEEDED run’s result READ can still return an unavailable error if its saved artifact cannot be read or verified; do not treat that failure as empty rows. Keep the returned selection in your own work. See Read results with an agent for direct Dashboard resolve and refresh.

Upload a document

Section titled “Upload a document”

Document Pages hold a Markdown (.md), notebook (.ipynb), or HTML (.html) file up to 20 MiB. Monomer displays the file without running notebook cells or HTML scripts, so run a notebook and save the outputs you want readers to see before uploading. Pages is not a general store for PDF, CSV, or other files.

  1. Select Pages in the sidebar, then open the destination folder. For the top level, open Search and choose Pages under Go to.
  2. Select Upload document and choose the file. Monomer fills in the title and format from the file; check them and add an optional description.
  3. Select Create document. When the upload finishes, the new document opens.
  4. Check its title and rendered content. Use Copy link to share it with your Workspace.

Original downloads the exact source file; opening it locally may run code, depending on the application you use. If an upload stops partway, the button changes to Retry completion or Retry publishing; select it rather than choosing the file again.

Replace content and read earlier versions

Section titled “Replace content and read earlier versions”

Open the document and choose Replace content, select the revised file, confirm its format, and select Add version. This adds a version and keeps the earlier file. To read an earlier version, use Version history, a panel beside the document on wide screens and a version list above it on narrow ones; select Load older versions if the one you need isn’t listed. Check the selected version before using Original.

An agent follows the document’s availableOperations to list its versions path, describes the advertised version create entry before adding a version, and reads versions for version metadata, including who finalized each one.

Organize Pages

Section titled “Organize Pages”
  • New folder creates a folder at the top level or inside the current folder. In the Pages sidebar, New folder at the end of the list also creates a top-level folder.
  • Open a Page’s actions to Rename, Move in Pages, Move up, or Move down, or to remove it. Only an empty folder can be deleted, so move or remove its pages first.
  • Selecting Pages in the sidebar shows the Pages folders and pages there without leaving the screen you are on. Selecting Pages at the top of that list returns to the Workspace sidebar.
  • Search finds a Page by title from either sidebar. Viewers and public readers, who don’t have Search, use Search pages above the list of Pages.

With an agent, read the resource and pass its EDIT entry to monomer_describe before building the patch. Folder placement is edited at workspace/pages/tree using paths under /placements, and title and description edits replace both /title and /description (use null to clear the description). Page kind and dashboard target can’t be edited.

Section titled “Share a link”

Copy link copies a link to the Page. Once a dashboard Page shows results, Link options chooses between Always latest results, the default, and Current results, which keeps the results you are looking at even after new ones arrive. Filter selections aren’t included in the link.

Retry agent changes safely

Section titled “Retry agent changes safely”

Agents create one commandId per intended directory change or document version, and reuse it only when resending the same request after losing the response. The response requestId is a trace identifier, not a key to send back.

Directory changes also need the revision the agent read, sent back as the same decimal string. For monomer_edit, use the top-level revision and commandId; for creation or deletion, use the advertised input’s baseRevision and commandId. If the directory changed, the agent reads the current tree, reviews the intended change, and submits a new command with a new key instead of replaying the old one.

The same operations work over REST: send the operation body to POST /v2/workspaces/{workspaceId}/agent/{operation} with a REST OAuth credential, putting workspaceId in the URL instead of the body. Agents can find Pages by title.

If rendering fails, check that the file matches the selected format and opens in its original application, and keep the visible error for troubleshooting.