How BytesMap fits together
Sources, queries, views, dashboards and workflows—each with a clear job.
BytesMap separates data access, reusable presentation and explicit effects. You can use the visual builder, an agent or the SDK to work with the same saved definitions.
The pieces
| Object | What it owns | Example |
|---|---|---|
| Source | Connection configuration and query safety limits | A read-only PostgreSQL reporting connection |
| Query / data flow | Reads, parameters, transformations and selected output | Releases grouped by outcome |
| Component | One configured visual or control | Donut chart, table, metric, form or button |
| View | A reusable section's datasets, components, bindings and interactions | Release outcomes and its drilldown action |
| Dashboard | Placed views, layout, shared inputs and publication | Account operations |
| Workflow | An explicit sequence of reads, rules and effects | Prepare an investigation and notify a channel |
| Project | Organization and inherited item access inside a workspace | Customer support |
A view can contain more than one component when they belong together. Three metrics derived from one summary query can share one view and one result. Independent sections can be separate views. A details panel is a presentation of a view or composition; it does not become an extra dashboard section just because it can open.
Follow the data
A source query produces a result. A component maps fields from that result. A selection can supply declared inputs to another view or a workflow. Those mappings are saved configuration, not customer-specific code.
Layout does not define execution order. Dataset bindings and dependencies do. Several components can reuse the same dataset without creating several copies of its query. Different source requests still perform distinct database work; use query cost to inspect it.
Saving, reading and acting are separate
Saving a definition records its configuration. Run or Load data performs an authorized read. Clicking a configured action can run a published workflow. Arranging nodes, inspecting a flow and opening settings must not submit an action.
A dashboard publication freezes its approved dependencies and workflow revisions. Editing a draft does not silently update what viewers run. Current access still applies to published content.
One view, several presentations
The same saved view can appear in a dashboard, a side panel, a centered modal or a page. Its inputs and bindings stay the same. Back navigation returns through the destination history; a URL can reopen a destination using the current user's access.
The flow canvas is an inspection and authoring surface. Expanding a reference shows its underlying steps. It does not create a second view or run another query.