Public vs Private Maps: Choosing the Right Sharing Option for Your Project
Try tracking sensitive internal data and public-facing info in the same spreadsheet and you'll end up with either too much exposed or two files that never quite match. Neither is a great option when the whole point of the data was to keep everyone on the same page.
With MAPOG, the same dataset that powers the internal operations map also powers the public community map. The sharing configuration inside Preview & Share is what separates them, role-based access for the private version and attribute selection for the public one, both drawing from one source and updating simultaneously whenever anything changes.
What Each Configuration Controls
Setting a map to Private means only people you've explicitly invited can open it. Within that, Admin gives full control, Editor lets field members update data directly on site, Viewer gives read-only access to stakeholders who need to see the full dataset without being able to change anything. For anyone outside the organization, Add Member handles the invitation with the same role options. Switching to Public opens the map to anyone with the link, but Selected Attributes controls exactly which fields they see. Sensitive operational columns stay unchecked. Public-safe fields get checked. The layout, toolbox, and search options can all be adjusted to suit a public audience before the link goes live.
Why It Actually Works
A field volunteer updating a site's status from Inactive to Active doesn't have to think about the public map. A community member opening the public link sees current information without seeing anything operational. Neither audience has to navigate information meant for the other, and there's never a second file to maintain. Healthcare networks use this for public clinic locators alongside internal staff maps. Government teams use it to publish resident-facing infrastructure status while keeping inspection records internal. NGOs use it for almost every community project they run.
The dataset is always the same. The sharing configuration is what determines who sees which part of it.
