Skip to main content

Saved views

Save the reads behind an assistant answer as a named view that runs them again with your access, then order it, share it and pin it to your Dashboard.
Open it fromPersonalSaved viewsRole:Any signed-in userConsole address: /personal/saved-views

A saved view keeps the reads behind an answer from the Console assistant, the chat that answers from your organisation's data. The reads are the queries that drew the answer's tables and figures. Each time the view opens, every block, one table or set of figures, runs its read again with the access of whoever opens it, so the view shows current data under that person's own permissions. You name your views, order them, share them with the organisation and pin them to your Dashboard.

The Saved views page before any view is saved, with its “No saved views yet” message.

Once you save a view, the page lists your views and the views shared with your organisation beside the blocks of the selected view.

Steps

Save an answer as a view

Ask the assistant a question that draws at least one table or one set of figures, then select Save as view under the answer.

  • The dialog reads “Save this answer as a view” and states what the view keeps: “A view keeps the reads behind this answer, not their results. Each time it opens it reads them again, with what you can see then.”
  • Name starts as your question. A question longer than 80 characters is cut to its first 79 and ends with “…”. Change it before you save. A name holds 1 to 80 characters, on save and on rename.
  • A block is kept only when its read can be run again: holders, events, holdings, assets, markets, orders, the audit trail, and figures. A rule reading and a check are not offered. A view holds between 1 and 6 blocks.
  • A table is kept only when the answer cites at least one of its rows. The view keeps the first 6 blocks. From each block it keeps the identifiers of the first 5 cited rows or the first 8 figures, the read's route, the input it ran with and the units of its figures. It keeps no row values and no answer text, but a cited row's identifier can be a holder's wallet address.
  • The platform checks every block before it stores the view: the route must be one that block kind runs again, a rows block must name rows of its own kind, a figures block must name figures of its own read, and an input may hold at most 2,000 characters. When one block fails, the platform refuses the whole view.
  • A save past 50 views of your own is refused. In the Console the dialog shows only “The view could not be saved.” The Platform API refusal says “You have 50 saved views. Remove one to save another.”
  • The view stores the scope the answer read, and the platform checks that you can still read that scope when you save.
  • After a save the button becomes Open saved views, which opens the new view.

Open Saved views

Select Saved views under “Personal” in the sidebar. With no views yet, the page says “No saved views yet” and explains how to save one from an answer. Otherwise it lists your own views and the views shared with your organisation in your order, with the selected view's blocks beside the list. The page lists at most 100 views. On a narrow screen the list scrolls sideways above the view instead.

Read the blocks of a view

Each block runs its read again with your access and draws the rows the view kept, as the same table or figure tiles the answer showed.

What shows in place of a block
Why
“You cannot see this part of the view.”
The read was refused for you. The other blocks still draw.
“This part of the view could not be loaded.”
The read failed for another reason. Try again runs it again.
“This part of the view cannot be shown here.”
The page cannot draw that kind of block.

In a view another member shared, the platform also filters each table by your own access. Each time your views load, on this page or under “Pinned views” on Dashboard, the platform runs each table's read again as you and keeps only the cited rows that read returns now, so you never see the identifiers of rows you cannot read. A table whose read is refused keeps its place and shows “You cannot see this part of the view.” A read that fails shows “This part of the view could not be loaded.” with Try again, and one that returns none of its cited rows draws no rows. Figures blocks, and every block of your own views, are not filtered this way.

Order, share and remove a view

Each view has an Actions menu. Every view you can see offers “Add to home” or “Remove from home”. It also offers “Move up”, except on the first view in your list, and “Move down”, except on the last. Your own views also offer “Rename”, “Share with the organisation” or “Stop sharing”, and “Remove view”.

  • A shared view carries a Shared badge, and the list names who shared it. A pinned view carries an “On home” badge. Only the owner renames, shares or removes it. “Stop sharing” removes the view from every colleague's list and home.
  • Sharing shows every member of the organisation the view's name and the scope it reads. A member sees a cited row's identifier only when their own read returns that row, as Read the blocks of a view describes. The name starts as your question, so rename the view before you share it if the question names something private.
  • Remove view asks “Remove <name>?” and states “The view is removed for you and for everyone it is shared with. The data it reads is not changed.”
  • A view you have not moved sits after the views you ordered, newest first. Your order and your home placement are yours alone, shared views included, and sharing a view never changes a colleague's list or home.
  • A list that fails to load shows “Saved views could not be loaded.” with Try again. A rename, share, move or remove that fails shows “The change could not be saved.”

Pin a view to home

Add to home puts the view on Dashboard under “Pinned views”, below the panels that need you and what changed, with its blocks and an “Open view” link. “All saved views” opens the full page. With views but none pinned, “Pinned views” says “No saved views on home yet”. Dashboard explains the panels above it.

Views built from a period summary

A figures block saved from a period summary reads again through the period summary read, with the asset and the window the view stores. A trailing period, such as the last 7 days, reads up to the moment the view opens. A window with fixed dates reads the same period each time. A view never stores the totals, because they age and a reader whose access changed would see numbers they may no longer open.

The table toolbar of Holders, the blocklist, Users and Actions has a “Saved views” menu of its own, which keeps filters, sort and columns under a name. Tables covers that menu.

Troubleshooting

The list says Saved views could not be loaded

The read of your views failed. Select Try again.

A rename, share, move or remove fails

The platform refused or could not store the change. Repeat it. Only the owner of a view renames, shares or removes it.

The dialog says The view could not be saved

The platform refuses a view past 50 views, a block it cannot run again, or one whose scope you can no longer read. Remove a view you no longer need, or save an answer that cites rows of a supported table.

Was this page helpful?