Embed and reuse views
Compose saved views while preserving input mappings, publication and access boundaries.
A saved view can appear inside another view, as a dashboard section, or as a destination opened in a page, drawer or modal. These placements reuse the same definition, bindings and renderer.
Embed a saved view
Add a View component and select the saved target. Map the child's declared inputs explicitly. For example, map an account detail view's accountId to the selected account's ID.
Each placement keeps its own filter, form and selection state. Refresh preserves mounted content. Changing the incoming record resets local filter overrides for that placement so the previous account's selection does not leak into the next one.
Use an interaction instead of an embedded component when the content should open only after a click. Chart, table and list actions share the destination and parameter mapping model. A named menu action and a primary selection action can open different destinations.
Publish the complete composition
Dashboard publication freezes recursively referenced view definitions, queries and reviewed workflow revisions. Editing a child draft does not silently change a published parent. Review and republish the parent when you want readers to use the change.
Embedding cycles are rejected. Ordinary navigation loops can be valid: a detail view may return to or open a related view without recursively rendering it inside itself.
Preserve the access boundary
A parameter such as accountId is data, not proof of authorization. The server resolves the saved reference path and checks current permissions for the caller and published dependencies. A client cannot gain access by replacing the target ID or overriding a parent-mapped input.
When integrating with another application's data model, that application must also enforce its record-level rules in the source or authorized backend. BytesMap workspace permissions do not automatically infer which customer rows belong to an external user.
Integrate from code
Use the HTTP/native SDK and CLI for the implemented operation surface. The repository's packages/ui owns the chart and view runtime shared by product hosts; its host adapter supplies transport, navigation and authorized submissions.
packages/ui is currently a private workspace package. A separately published @bytesmap/react distribution and a guest-embedding SDK are not available. Do not copy older proposal snippets as supported installation or authentication instructions.
For binding paths, shared datasets and publication details, read view composition.