Security settings
To adjust your project's security settings:
From here you can enable or disable Attack Mode, Vercel Support Code Visibility, and Git Fork Protection.
Only you and authenticated members of your Vercel team can see the build logs and source code of your deployments. This also applies to the following paths on your deployment URLs and custom domains:
/_src: Displays the source code and build output./_logs: Displays the build logs.
Both paths redirect to the Vercel dashboard, where visitors must log in to Vercel as a member of your team.
This protection is always on and covers all of your deployments, including older ones. You can't disable it for a project or for a single deployment.
Vercel Support Code Visibility is available on Enterprise and Pro plans
This setting controls whether the Vercel Support team can view your deployment's source code. By default, it's disabled, so the source code is visible only to you and your team. The Vercel Support team might ask you to enable it to troubleshoot specific issues related to your source code. To allow them, open Security, enable Vercel Support Code Visibility, and click Save, then confirm by entering your team-slug/project-name and clicking Enable.
If you receive a pull request from a fork of your repository, Vercel will require authorization from you or a Team Member to deploy the pull request.
This behavior protects you from leaking sensitive project information such as environment variables and the OIDC Token.
You can disable this protection in the Security section of your Project Settings.
This feature allows you to secure access to your backend services by using short-lived, non-persistent tokens that are signed by Vercel's OIDC Identity Provider (IdP).
To learn more, see Secure Backend Access with OIDC Federation.
This section lists the recently deleted deployments of your project. You can restore a deleted deployment during its recovery period. To learn more, see Restoring a deleted deployment.
To set a limit on how long Vercel keeps older deployments for your project, use the Deployment Retention Policy section of your project's Build and Deployment settings. To learn more, see Deployment Retention Policy.
Was this helpful?