Places¶

The Administration → Places cockpit (/governance/places) is the central spot where admins maintain the public places inventory: review citizen proposals, handle reports, correct entries, hide them, or create them directly. What places are from a user's point of view is described in Features → Places.

When something is waiting for you — a new proposal or an open report — the Governance hub shows this live as a red attention badge on the Places row.

Screenshot: the Places cockpit with facets and detail panel — assets/screenshots/admin/admin-places.png

The cockpit at a glance¶

At the top you choose a facet — it determines which entries the list shows:

Facet	Content
Proposed	New citizen proposals waiting for your decision
Published	All publicly visible places
Hidden	Places temporarily taken out of the public view (reversible)
Rejected	Rejected proposals
Reported	All open reports from visitors

Within a facet you can filter by free text (except on Reported). Clicking an entry opens the detail panel with all information and the matching actions. Facet and selection live in the address bar — so you can share a specific view as a link.

Decisions and their effect¶

Action	Effect
Approve	The proposal is published and immediately publicly visible.
Reject	The proposal is rejected and never becomes public. Rejected entries are removed automatically after a retention period (data protection).
Bulk approve / bulk reject	On the "Proposed" facet you can select several entries and approve or reject them in one step — handy during spam waves.
Hide	A published place disappears immediately from map, list, and search — the fast, reversible emergency action (e.g. on a justified report).
Restore	A hidden place is published again.
Edit	Correct details (name, category, attributes, description, opening hours, image) and location (pin, address).
Remove permanently	The place is irrevocably deleted.
Create place	Admins can also create places directly — no proposal step, published immediately.

Three principles behind this:

Your approval is the single control. No proposal is published automatically. When approving, check for duplicates (the cockpit shows similar places nearby) and make sure no private addresses or protection facilities get published.
Reports never hide automatically. Whether a reported place disappears is always your decision — "Hide" gives you a fast, reversible measure for that.
Proposers stay private. Who proposed a place is neither publicly visible nor part of the entry.

The Reported facet lists all open reports — each with a reason (e.g. "no longer exists", "wrong location", "duplicate entry") and an optional message from the reporting person. Per report you decide:

Resolve — the report has been dealt with (e.g. details corrected or place hidden).
Dismiss — the report is unfounded.

Handling a report does not change the place itself: if you also want to hide, correct, or remove the reported place, use its own action for that.

Organisations on the map (org pins)¶

Organisations that maintain an address with a map position in the directory also appear as a pin on the public map — their pin leads to the organisation profile. In the cockpit these entries flow through the same states as ordinary places; the detail panel shows the originating organisation, and content changes are made on the organisation profile itself.

An instance policy in the instance settings controls the review:

Default: map pins set by the organisation itself appear immediately; only positions derived automatically from the address go through the Places review first.
"Always review org pins": every organisation pin — including a manually placed one — waits for your approval first.

Map, default view, and address search¶

The map as a whole is optional — a hub without a configured map shows the Places section as a fully-featured list. For operators:

Map default view — you set the starting viewport and zoom level for visitors without a saved view in the instance settings (only visible when the map is configured): pan the map to the desired area, set the zoom, save.
Map service & attribution — which tile service renders the map (including the legally coupled attribution) is configured when operating the instance — see Self-Hosting.
Address search (geocoder) — optional; disabled by default. Setting a position by pin always works, even without address search. A self-hosted geocoding service (e.g. Nominatim) is recommended; if a public service is used instead, locali throttles requests (1 request/second) and points out in the cockpit that address input leaves the instance.

Frequently asked questions¶

Question	Answer
What happens to rejected proposals?	They remain traceable in the "Rejected" facet for a while and are removed automatically after a retention period.
Does a report hide the place automatically?	No — never. Hiding is always a deliberate admin decision; the report only draws your attention.
Can I bring back a hidden place?	Yes, any time via Restore. Only "Remove permanently" is irrevocable.
Why can I not edit an org pin directly?	Because its data comes from the organisation profile. Changes happen there; in the Places cockpit you only control visibility.
Do I have to pay for the map or need an account with a map provider?	No. The map is optional and works with self-hosted tiles; without any map, the list remains fully usable.