Access protection
Restrict who can open your Snapvisor deployment URLs. Learn the public, standard, and all-deployments protection levels.
Deployment URLs can be public, or locked to people who are logged in and have access to the project. Log-in protection keeps preview environments out of the wrong hands.
Protection levels
- Public — anyone with the link can open the deployment. No login required.
- Standard protection — every deployment is login-protected except production custom domains, which stay public.
- All deployments — every domain, including production, requires login. This level needs a team and isn't available on personal accounts.
How log-in protection works
When a deployment is protected, opening its URL requires being signed in to a Snapvisor account that has access to the project. Team members get in transparently; everyone else is stopped at the login screen.
The strictest level protects even your production domain, so make sure your reviewers have project access before you enable it.
URLs and domains
Pick the subdomain your project's production deployment is served on. Learn the slug rules for Snapvisor production domains.
Self-hosting
Run your own Snapvisor instance with Docker Compose - the services it needs, the environment variables it refuses to boot without, and how to point the SDKs at it.