From de18477ce323bfeecfa5b3d666f4e3697115e6f2 Mon Sep 17 00:00:00 2001 From: Copple <10214025+kiwicopple@users.noreply.github.com> Date: Thu, 24 Aug 2023 13:24:55 +0200 Subject: [PATCH] Update apps/docs/pages/guides/auth/row-level-security.mdx Co-authored-by: Raminder Singh --- apps/docs/pages/guides/auth/row-level-security.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/pages/guides/auth/row-level-security.mdx b/apps/docs/pages/guides/auth/row-level-security.mdx index 679bcf97a20..92f25f1d8ae 100644 --- a/apps/docs/pages/guides/auth/row-level-security.mdx +++ b/apps/docs/pages/guides/auth/row-level-security.mdx @@ -111,7 +111,7 @@ Initializing a client with a Service Key will not override RLS if a user token i ### Always enable RLS on public tables -You should _always_ enable RLS on tables created in a public schemas. This is considered "default safe". Unfortunately this is not enabled by default on Postgres, so you will need to keep this in mind - especially if you are using the SQL Editor or database migrations. RLS is already enabled by default if you create a table using the Table Editor. If you want to allow public access to a table, just add a Policy with `true`: +You should _always_ enable RLS on tables created in a public schema. This is considered "default safe". Unfortunately this is not enabled by default on Postgres, so you will need to keep this in mind - especially if you are using the SQL Editor or database migrations. RLS is already enabled by default if you create a table using the Table Editor. If you want to allow public access to a table, just add a Policy with `true`: ```sql create policy "Allow public access"