Maps
A map shows things you already hold — branches, installations, service partners, delivery addresses — on a base layer. It is a media type, so it has fields, a display and permissions like everything else.
Back office → Configuration → Maps for the base layers, Structure → Media types for the map type itself.
Where the points come from
Two ways, and the difference matters:
| Source | Behaves like |
|---|---|
| Points entered on the map item | Content — you place them, they stay |
| A listing | A query — the map shows whatever matches, now |
Prefer the listing
A map fed by a listing cannot go stale. Add a branch to the records and it is on the map; close one and it is not. A map with points typed onto it is a second copy of your addresses, and second copies drift.
Geo fields
A record carries a location in a geo field — a coordinate pair, usually alongside a normal address field. The address is for people; the coordinate is for the map.
Both, not one: an address geocoded on every render is a request per point and a dependency on somebody else's service; a coordinate with no address is unreadable to the person who has to drive there.
Base layers
The base layer is the map underneath. It is configured, not fixed — which matters commercially as much as technically, because tile providers have licences and rate limits, and the right answer differs per customer.
A base layer is somebody else's service
Check the licence and the usage limits of whatever you configure. A map that works in testing and rate-limits on a launch day is a configuration problem, not a platform one.
What a visitor sees
A map is rendered live, so it follows the same visibility rules as the records behind it: an unpublished branch is not a point, and another organization's addresses are never on your map.
On a phone
Maps scroll and zoom inside their own frame. The page never scrolls sideways — that is a rule of the platform, not a per-map decision.