Access policies

Read what each restriction on the Restrictions tab refuses, and what keeps working while it is on.

Part of the beta programme. If it is off for your organisation, the policies already set keep applying; you can relax or clear them, but not add one or make one stricter.

Policy	What it refuses	What still works
External sharing prohibited (every project, or named projects)	New shares, client access, review invitations and deliveries, and anything that would widen or extend them	What was already shared keeps working until someone ends it. Ending it, a withdrawal, a reminder and the release of a hold are never refused
Confidential projects	Opening a project without a role on it, or one at its branch if you choose that	Organisation-wide roles, the owner's included, reach it only while their holder has emergency access switched on. The audit trail still lists what happens on it to the people who read the trail
Sensitive downloads	Downloading originals and exports for roles you do not name, or for people whose access is only a project role. The map's copy of a delivered raster is limited the same way. Making a delivery, a client access that includes downloads, or a share or link that allows the download is refused to them too	The owner is never refused
Fresh sign-in for sensitive work	Managing or inviting people, lending a role, billing, the audit trail or access, unless you signed in with your password and two-step sign-in in the last 8 hours in that browser session	Anyone asked can use Sign in again

Details

• A delivery counts as sharing because it lets another organisation read the release.
• Under Sensitive downloads, a share that allows the download cannot be edited, moved to a new release or extended by a role the policy refuses. Switching its download off is always allowed.
• Turning Fresh sign-in for sensitive work on asks for your own password and code.
• Every policy change asks for a reason and is listed under the tab's history.
• To give a role or set one up, see Create a role.