Editable layers — editing hosted data everywhere

What an editable layer is¶

A Hyz Layer is read-only until its owner switches editing on. From then on the layer's rows are the live copy: people with edit permission change them in the browser (the data item's Editing panel), in Hyz Desktop (check the layer out, work offline, sync) and from Hyz Field (a campaign feeds the layer with approved records). The original upload is never modified; the history is an edit log plus the snapshots you take. The item wears an Editable chip wherever it is listed.

This page is the overview. Each part of the model has a page of its own, written to be read on its own, in this order:

Section	Read it when
Who may edit: permissions and locks	you are deciding who gets to change what, or an edit was refused for permission
The rules an owner sets	you are switching editing on and shaping how people may edit
Editing in the browser	you will correct features on the item's page
Editing offline in Hyz Desktop	you will check a layer out, edit offline and sync
Feeding a layer from Hyz Field	collectors add points on site and approved records should become features
History, snapshots and restore	you need to see who changed what, keep a state, or go back
Why an edit was refused	you have a reason code on screen and want the fix

Before any of that, editable or not says which data can be made editable at all, and kinds of data names every shape the platform knows.

Two questions, both must say yes¶

Every edit is checked twice, on the server, on every save, and both checks have to pass:

1. May this person edit this layer? That is the data item's permissions: an editor or above on the item, or a contributor or above in the owning organization. A deny on the item wins over any role; an expired grant behaves like no grant.
2. May this feature be edited at all? That is the feature's own lock plus the layer's rules. A locked feature refuses everyone, the owner included, until it is unlocked.

Every client renders what the server granted and decides nothing itself. The Editing panel shows what you may do as chips (create, edit, delete, geometry); a chip that is crossed out carries the reason when you hover it, and the Hyz Desktop sync dialog shows the same chips.

The three places editing happens¶

Place	Best for	Works offline	How a change travels
Browser, the item's Editing panel	small corrections, locks, rules, snapshots	no	your changes are collected and sent together when you press Save changes; the server answers per change
Hyz Desktop	large layers, long sessions, field laptops	yes	check the layer out, edit with the full toolset, Sync sends your changes and receives everyone else's
Hyz Field	new points collected on a phone	yes, for collection	a campaign targets the layer; approving a record creates its feature with the collector as creator

All three write to the same rows through the same checks, so a lock set in the browser holds in Hyz Desktop, and a rule change applies to the next sync from every device.

What changes when editing is on¶

• The layer counts against your plan's editable layers allowance, and every applied change against edits per month.
• A new file version cannot be uploaded onto the item: it would replace the live rows. Take a snapshot or switch editing off first.
• The publication's revision moves when people edit, so maps that follow the published layer see the edits; a PMTiles archive built before goes stale.
• The feature count on the item follows the live rows.
• Every applied change, lock and unlock lands in the history, and the layer carries a sync version that Hyz Desktop uses to ask for "everything since".

Switching editing off keeps the rows as they are and makes the layer read-only again; checked-out copies can no longer sync, and uploads are allowed again.

Where things live¶

What	Where
Switch, rules, locks, history, snapshots	the data item → Editing
In-browser editing	the same panel, Edit tab
Offline editing and sync	Hyz Desktop → Browse data items → Check out, then Sync in the Field pane
Feeding a layer from a campaign	the campaign's page → Feed a layer
Finding editable layers	/data/items; an editable item wears the Editable chip on its card
Plan limits	Limits: editable layers per owner and edits per month