Set team security policies in Team Settings - (Team web app)

Where the security policies live

The Team Settings page holds two cards. The first card is for your team name and description. The second card, Security Settings, is where you control how members save maps. Only owners and admins can change these. The page also shows your Team Code at the top.

You open this page from the Team Settings section of the team portal.

Team Map Saving

These two toggles control how team maps can be shared. They do not need SSO.

Allow Private Maps

When this is disabled, maps saved to the team can only be Secure or Encrypted. Private and Unlisted are not allowed.

Allow Password Access

When this is disabled, team maps cannot use an access password. Access is by team membership or explicit permission only.

Block Personal Map Saving

This policy routes a member's map saves to the team instead of their personal account. It works for members whose email matches one of your verified SSO domains.

You must verify at least one SSO domain first. If you have none, the page shows a warning with a link to verify a domain on the SSO settings page, and the toggle stays off.

When at least one domain is verified, the page shows:

• The list of verified domains and how many users each one has.
• How many users have verified domain emails.
• How many of their private maps would be affected.

Use the Block Personal Saving toggle to turn the policy on. When it is on, all map saves from affected users are saved to the team.

Migrate existing private maps

When you turn the policy on and affected users still have private maps, the page asks if you want to move them now.

• Click Migrate Maps to Team to move the existing private maps to the team.
• Click Skip to leave them as they are.

If maps are left behind, the page keeps a migration button so you can move the remaining maps later.