# Ensure anonymous sign-ins are disabled unless explicitly required

- Source: https://support.icompaas.com/support/solutions/articles/a_1790103908613431-ensure-anonymous-sign-ins-are-disabled-unless-explicitly-required
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [Supabase cloud](https://support.icompaas.com/support/solutions/c_1790103054038308) › [supabase checks](https://support.icompaas.com/support/solutions/folders/f_1790103067540538)
- Last updated: 2026-09-22
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Description**

Ensure the Allow anonymous sign-ins setting is disabled unless the application has a clear, documented need for anonymous users, such as guest shopping carts. If it is enabled, RLS policies must check the is\_anonymous claim to limit what anonymous users can do.

**Rationale**

Anonymous users are given the authenticated role, the same as real signed-in users. Existing RLS policies written for authenticated users will therefore also apply to anonymous users, who may gain access to data or actions they should not have. Anonymous sign-ins can also be abused to create large numbers of accounts and increase costs.

**Impact**

-   Prevents unintended access by anonymous users
    
-   Reduces abuse through mass account creation
    
-   Guest features that rely on anonymous users will stop working
    

**Default Value**

By default, anonymous sign-ins are disabled.

**Pre-Requisites**

-   Project Owner or Admin role
    

**Test Plan**

1.  Sign in to the Supabase Dashboard at [https://supabase.com/dashboard](https://supabase.com/dashboard).
    
2.  Select your project.
    
3.  Open Authentication in the sidebar and select Sign In / Providers.
    
4.  Verify that Allow anonymous sign-ins is disabled.
    
5.  If it is enabled without a documented need, follow the implementation steps.
    

**Implementation Steps**

1.  Sign in to the Supabase Dashboard at [https://supabase.com/dashboard](https://supabase.com/dashboard).
    
2.  Select your project.
    
3.  Open Authentication in the sidebar and select Sign In / Providers.
    
4.  Disable Allow anonymous sign-ins.
    
5.  Select Save.
    

**Backout Plan**

1.  Sign in to the Supabase Dashboard at [https://supabase.com/dashboard](https://supabase.com/dashboard).
    
2.  Select your project.
    
3.  Open Authentication in the sidebar and select Sign In / Providers.
    
4.  Enable Allow anonymous sign-ins.
    
5.  Select Save.
    

**Reference**

-   [https://supabase.com/docs/guides/auth/auth-anonymous](https://supabase.com/docs/guides/auth/auth-anonymous)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.