Sharing & publishing
Two independent switches govern who sees what: Ownership (Private or Organization) inside your org, and Publishing for the open web — apps only, with a clear exposure check.
Ownership: Private or Organization#
Every item is either Organization — visible to everyone in your org — or Private. New items start as Organization. Private is a real boundary, not just a hidden card: a private dataset’s data, tiles and exports are only accessible to you and portal administrators, everywhere — maps, dashboards, the Data Editor, QGIS. The owner (or an admin) flips ownership on the item page.
Thumbnails and story media stay reachable by direct link even on private items — don’t put secrets in a thumbnail.
Publishing: apps only, one switch#
Three item types can be published to the open web: dashboards, journeys and surveys. Maps, datasets and files never get standalone public URLs — they reach the public only inside a published app. Publishing is binary: an item is published or it isn’t, and unpublishing takes it down again.
- Publishing requires the Publisher or Admin role.
- The public URL is
https://your-org.orbgis.se/item-title— your org’s own subdomain plus a slug derived from the title. Readers need no login and no seat. - The publish sidesheet shows a QR code and a copy-link row.
- Surveys publish in two stages — an organization fill link first, the public web form second. See Surveys.
The exposure check#
Before anything goes live, the publish sidesheet lists every dataset that becomes publicly readable — the layers of every embedded map, plus related datasets — and flags any that are currently Private. Publication deliberately overrides Private for exactly those datasets, so the list is your moment to say no. Unpublishing restores the previous access atomically.
Sharing inside the organization#
Everything that isn’t Private is already visible to your whole organization in the portal — there’s no per-item member picking. Maps and apps have a Share button with an org link and QR code for quick handoffs. Folders don’t affect visibility at all; they’re private to each user.
A published app is readable by anyone with the link — treat the URL itself as public. Check the exposure list before publishing, especially when maps embed layers owned by colleagues.