Secure Your Resource

Secure a native integration resource by controlling where projects can connect to it. When you set a resource to Production only, Vercel removes non-production access and protects credentials as Secret environment variables, so secret values are not readable from the dashboard or CLI.

Confirm these requirements:

• The resource has an Allowed Environments section in Settings
• You have a Member or Owner role to set a resource to Production only
• You have an Owner role to allow non-production environments again
• You have reviewed existing non-production project connections

To secure a resource:

1. From your Vercel dashboard, open Integrations.
2. Select Manage for the integration, and then open the installed product resource.
3. Open Settings and find Allowed Environments.
4. Select Production only.
5. Review the affected non-production connections.
6. Check the acknowledgment that non-production connections will be removed.
7. Select Save.

After save completes, Vercel removes Preview, Development, and Custom Environment targets from existing connections. Connections that include Production remain connected in Production only. Connections that do not include Production are disconnected.

When a resource is secured with Production only:

• New connections to Preview, Development, or Custom Environments are blocked
• Existing Preview, Development, and Custom Environment targets are removed when you save
• Connection rows without a Production target are disconnected
• Resource credentials are protected as sensitive values and are not readable in the dashboard or CLI

If you need broader access later:

This operation requires the Owner role.

1. Open the resource Settings page.
2. In Allowed Environments, select an option that includes non-production environments.
3. Select Save and complete the required multi-factor authentication (MFA) challenge.
4. Reconnect any projects that were fully disconnected from the Projects tab.

If save is blocked:

• Confirm you selected the acknowledgment checkbox
• Review the listed non-production connections before retrying
• Reopen the resource page and verify your latest Allowed Environments setting