Apps & Dashboards
Apps & Dashboards presents data and work a Workspace already owns. An App opens installed software. A Dashboard saves a view. Reads, writes, and report sends keep their own checks.
Boundary
Apps & Dashboards owns the experience and its delivery. Records & Lists owns the Records it reads. Installable Products owns Product installation. Labs & Modeling owns the study evidence that may support a release. A working view does not prove a successful writeback or report delivery. Each outcome needs its own result read back.
Services
Apps & Dashboards has two entry points for understanding an experience. Start with its saved form, then inspect its data and effects. The Console opens these experiences at /apps and /dashboards.
| Reader decision | Start with |
|---|---|
| Choose or author an App or Dashboard. | Apps and dashboards explains saved views, installed versions, sharing, and publishing. |
| Explain a read, write, or scheduled report. | Data, writeback, and schedules separates data rights from external effects. |
Start here
For Apps & Dashboards delivery, build and publish an experience and check what the intended viewer receives. If a view, provider, or writeback fails, recover app delivery selects the repair from its evidence. To inspect an installed App before opening it, the bootstrap contract defines the HTTP read, permission, and response. Consult a native Surface guide for availability.
Next steps
- API reference owns exact App and Dashboard requests, permissions, results, and errors.
- The Console guide explains access and navigation for a builder or viewer.
- The API guide explains calls to the supported App and Dashboard contracts.