Skip to main content
A d0 dashboard contains manifest.json and local web assets. It runs in a WebView and uses window.gatetrix for supported data capabilities.

A public-data manifest

This example matches the permissions used by the Hacker News sample. Place an index.html file beside the manifest.
Use a distinct stable id for your own dashboard. Bundle scripts and styles locally. The dashboard cannot use Node APIs, launch a shell, access arbitrary files, load remote scripts, or make arbitrary direct network requests.

JavaScript bridge

These calls run inside a dashboard after the corresponding capabilities have been declared and the version trusted:
For a dashboard connected to Access, discover its available tools and call a declared tool using its current input schema:
Public requests are bounded HTTPS GET requests. For connected services, use Access and declare the specific tools or connector operations. The tool list does not grant new permissions.

Local storage

Add a storage declaration inside permissions when the dashboard needs saved settings or records. This is a manifest fragment:
Then use the bridge:
Storage belongs to the stable dashboard ID and declared collections. It is not a secret store. Keep API keys and tokens out of preferences and records.

Trust and failures

Changes to dashboard files require review of the new version before it can use runtime data capabilities. Builder access does not grant trust. Handle loading, empty, denied, and failed states visibly. For a failed or uncertain write through Access, inspect the result or approval request before retrying. Use Runtime Audit to investigate host calls associated with a version.