What password-protected maps does
- Gate any shared map behind a password
- Each map has its own independent password
- Set, change or clear the password whenever you like
- Passwords are stored as a secure one-way hash
- Share with clients or teams without going fully public
- Switch a map back to public in a click
Password-protected Maps in GeoMaps
Sometimes a map should be shareable but not public. Password protection puts a gate in front of a shared map: visitors see a prompt for the code and only get through if they have it, so you can hand a link to a client or a team without exposing it to the open web.
Each map has its own password, which you can set, change or remove at any time. Passwords are stored securely as a one-way hash rather than as plain text, so the code itself is never kept in readable form.
It's part of GeoMaps' generate maps tools, so it works hand in hand with the rest of your map.
Where password-protected maps helps
Client deliverables
Share a map with a single client behind a password so only they can see their data.
Internal-only maps
Protect an operations map meant for staff so the link can't be opened by anyone who stumbles on it.
Pre-launch sharing
Show a map to a few stakeholders for review before deciding whether to make it fully public.
Password-protected Maps FAQ
- How does password protection work?
- When a map is password-protected, visitors who open the link are asked for the code and only see the map if they enter it correctly.
- Is the password stored securely?
- Yes. Passwords are saved as a secure one-way hash rather than as readable text, so the code itself is never stored in plain form.
- Can each map have a different password?
- Yes. Password protection is per map, so every shared map can have its own code.
- Can I remove the password later?
- Yes. You can change or clear a map's password at any time to update access or make the map public again.