One path for data on Haiyz: a file becomes a data item, a data item becomes a service — read-only or editable — and the service is what maps, field campaigns and dashboards use.
Open ServicesData on Haiyz moves along one path, and every product reads from the same place on it:
A file that was never made into a service can still be looked at: dropped into the Workspace, analysed, printed. It cannot feed a dashboard or a campaign. That is not a limit to work around; it is what keeps every dashboard live and every campaign writing into one truth.
On a data item, choose Make a service. The sheet asks for four things:
| Read-only | Editable | |
|---|---|---|
| What it is | A published view of the layer | A layer that Hyz Field campaigns and live editing write into |
| Use it for | Reference data, boundaries, anything you publish but do not maintain | Anything collected or maintained in the field |
| Changing later | Publish again | Publish again |
The choice between read-only and editable is made here, once. An editable service needs editing to be on for the instance; where it is not, the sheet says so before anything is published.
If the layer is not online yet the service waits as preparing and publishes itself when the import finishes — you do not have to come back and press anything.
In a map. In the Workspace, add the layer from Published layers and save the map: the layer goes in live, reading the service, and the map is a service map. A map made from plain files is a static map — see Static maps and service maps.
In a field campaign. On the campaign, choose the target layer: only editable services are offered, and approved records become features of that layer.
In a dashboard. Pick the data item, a service map, or a whole data room as a source; every widget then reads the service live.
Outside Haiyz. A service has a stable address. Its page lists the tiles, the features API and the open-standards endpoints, with a copy button on each.
A data room bundles data items. When every item in it has a service, it is a service room and the three products take it whole: a map attaches it and reads its unpinned items live, a dashboard picks it as one source, a campaign narrows its target to the room's editable services. Room roles still decide who may open the room.
A private service is shared with a person, a group or the whole organization, as can use or can use and share. Sharing a service never opens the data item behind it.
A service that maps, workspaces, dashboards or campaigns still read cannot be unpublished by accident: Haiyz names what reads it and asks you to confirm. Unpublishing keeps the address; publish again later and everything that pointed at it works again.