netlify-access-control

Selects the correct Netlify protection layer for restricting site and preview access.

Updated May 19, 2026
One-click install
npx skills add https://github.com/costrict-plugins-repo/anthropic-netlify-skills --skill netlify-access-control-costrict-plugins-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: netlify-access-control
Source: https://github.com/costrict-plugins-repo/anthropic-netlify-skills/tree/main/codex/skills/netlify-access-control
Command: npx skills add https://github.com/costrict-plugins-repo/anthropic-netlify-skills --skill netlify-access-control-costrict-plugins-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Netlify has three unrelated mechanisms people call "auth" — Netlify Identity for app users, Password Protection / Project visibility for site perimeter access, and Team/Org SAML SSO for dashboard login — and choosing the wrong one wastes hours. This Skill disambiguates them and routes you to the correct protection layer for your goal. ## Core Features & Use Cases - Layer selection: Maps goals like password-protecting a site, restricting previews, or requiring SSO to the correct Netlify feature with plan-specific UI naming (Project visibility vs Password Protection). - Dashboard checklists: Provides exact dashboard paths and step-by-step checklists for setting passwords, team login protection, and SSO enforcement, since these settings have no API, CLI, or MCP access. - SSO session troubleshooting: Explains the 1-hour SSO token expiry, 401 symptoms, and how to use the Netlify-Site-Protection-Expires-In header to trigger re-authentication. - Use Case: A developer wants only company employees to reach a staging site while keeping per-user logins in the app. The Skill routes them to team login protection for the perimeter and the netlify-identity skill for in-app auth, warning about the unavoidable double login. ## Quick Start Ask the agent which Netlify protection layer to use for password-protecting your deploy previews while keeping production public.

Frequently Asked Questions about netlify-access-control

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I password-protect a Netlify site?

Set a password via Project configuration > General > Visitor access > Project visibility on Credit-based plans, choosing Password and a scope of Production and previews or Previews only. On Enterprise or legacy plans, use Password Protection with Basic password protection instead.

What is the difference between Netlify Identity and Password Protection?

Netlify Identity handles app-user login, issuing nf_jwt tokens for users inside your app. Password Protection and Project visibility control whether a request can load the site at all, acting as a platform perimeter. Their sessions are completely separate with no shared cookie or token bridge.

Can I configure Netlify site protection via API or CLI?

No. Password Protection, Project visibility, and SSO settings have no public API, CLI command, or MCP tool. All changes must be made through the Netlify dashboard using the documented configuration paths.

Why does my SSO-protected Netlify site return 401 errors mid-session?

SSO auth tokens expire after one hour, causing the site to return HTTP 401 once the token lapses. Read the Netlify-Site-Protection-Expires-In response header and trigger re-authentication before it reaches zero.

How do I require SSO to view a Netlify site?

First configure Organization or Team SAML SSO, then enable Password Protection with Team login protection. Set the SSO configuration to Only SSO allowed (strict) to force SSO for all viewers.

Can I combine Password Protection with Netlify Identity for company-only access?

Yes, but the two layers require separate logins with no session bridge, creating a double login. For single sign-on, prefer invite-only Netlify Identity or the Auth0 extension federating to your corporate IdP instead.