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.