diff --git a/examples/slack-clone/nextjs-slack-clone/README.md b/examples/slack-clone/nextjs-slack-clone/README.md index 1feb31e23ee..12a3a0f578e 100644 --- a/examples/slack-clone/nextjs-slack-clone/README.md +++ b/examples/slack-clone/nextjs-slack-clone/README.md @@ -109,7 +109,7 @@ Users with the `moderator` role can delete all messages. Users with the `admin` ### Postgres Row level security -This project uses very high-level Authorization using Postgres' Role Level Security. +This project uses very high-level Authorization using Postgres' Row Level Security. When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions. When a user logs in, they are issued a JWT with the role `authenticated` and their UUID. We can use these details to provide fine-grained control over what each user can and cannot do. diff --git a/examples/todo-list/nextjs-todo-list/README.md b/examples/todo-list/nextjs-todo-list/README.md index 6abe010890b..2b04f4ffeae 100644 --- a/examples/todo-list/nextjs-todo-list/README.md +++ b/examples/todo-list/nextjs-todo-list/README.md @@ -37,7 +37,7 @@ The `anon` key is your client-side API key. It allows "anonymous access" to your ### Postgres Row level security -This project uses very high-level Authorization using Postgres' Role Level Security. +This project uses very high-level Authorization using Postgres' Row Level Security. When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions. When a user logs in, they are issued a JWT with the role `authenticated` and their UUID. We can use these details to provide fine-grained control over what each user can and cannot do. diff --git a/examples/todo-list/sveltejs-todo-list/README.md b/examples/todo-list/sveltejs-todo-list/README.md index b49c36dc207..f72c0cfc7c8 100644 --- a/examples/todo-list/sveltejs-todo-list/README.md +++ b/examples/todo-list/sveltejs-todo-list/README.md @@ -28,7 +28,7 @@ The `anon` key is your client-side API key. It allows "anonymous access" to your ### Postgres Row level security -This project uses very high-level Authorization using Postgres' Role Level Security. +This project uses very high-level Authorization using Postgres' Row Level Security. When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions. When a user logs in, they are issued a JWT with the role `authenticated` and their UUID. We can use these details to provide fine-grained control over what each user can and cannot do. diff --git a/examples/user-management/angular-user-management/README.md b/examples/user-management/angular-user-management/README.md index b7c924f8650..1f3dd7d2f5c 100644 --- a/examples/user-management/angular-user-management/README.md +++ b/examples/user-management/angular-user-management/README.md @@ -54,7 +54,7 @@ Run the application: `npm run start`. Open your browser to `https://localhost:42 ### Postgres Row level security -This project uses very high-level Authorization using Postgres' Role Level Security. +This project uses very high-level Authorization using Postgres' Row Level Security. When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions. When a user logs in, they are issued a JWT with the role `authenticated` and their UUID. We can use these details to provide fine-grained control over what each user can and cannot do. diff --git a/examples/user-management/expo-user-management/README.md b/examples/user-management/expo-user-management/README.md index c00e02db846..bec8ab1fecd 100644 --- a/examples/user-management/expo-user-management/README.md +++ b/examples/user-management/expo-user-management/README.md @@ -50,7 +50,7 @@ Run the application: `npm start`. ### Postgres Row level security -This project uses very high-level Authorization using Postgres' Role Level Security. +This project uses very high-level Authorization using Postgres' Row Level Security. When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions. When a user logs in, they are issued a JWT with the role `authenticated` and their UUID. We can use these details to provide fine-grained control over what each user can and cannot do. diff --git a/examples/user-management/nextjs-user-management/README.md b/examples/user-management/nextjs-user-management/README.md index 52b8958d581..4b3b7a407a7 100644 --- a/examples/user-management/nextjs-user-management/README.md +++ b/examples/user-management/nextjs-user-management/README.md @@ -64,7 +64,7 @@ Run the application: `npm run dev`. Open your browser to `https://localhost:3000 ### Postgres Row level security -This project uses very high-level Authorization using Postgres' Role Level Security. +This project uses very high-level Authorization using Postgres' Row Level Security. When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions. When a user logs in, they are issued a JWT with the role `authenticated` and their UUID. We can use these details to provide fine-grained control over what each user can and cannot do. diff --git a/examples/user-management/react-user-management/README.md b/examples/user-management/react-user-management/README.md index e130674be3d..4370ec623a2 100644 --- a/examples/user-management/react-user-management/README.md +++ b/examples/user-management/react-user-management/README.md @@ -56,7 +56,7 @@ Run the application: `npm run dev`. Open your browser to the url indicated in th ### Postgres Row level security -This project uses very high-level Authorization using Postgres' Role Level Security. +This project uses very high-level Authorization using Postgres' Row Level Security. When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions. When a user logs in, they are issued a JWT with the role `authenticated` and their UUID. We can use these details to provide fine-grained control over what each user can and cannot do. diff --git a/examples/user-management/refine-user-management/README.MD b/examples/user-management/refine-user-management/README.MD index 3d40da4f970..84b7682ff06 100644 --- a/examples/user-management/refine-user-management/README.MD +++ b/examples/user-management/refine-user-management/README.MD @@ -64,7 +64,7 @@ Run the application: `npm run dev`. Open your browser to `https://localhost:5173 ### Postgres Row level security -This project uses very high-level Authorization using Postgres' Role Level Security. +This project uses very high-level Authorization using Postgres' Row Level Security. When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions. When a user logs in, they are issued a JWT with the role `authenticated` and their UUID. We can use these details to provide fine-grained control over what each user can and cannot do. diff --git a/examples/user-management/solid-user-management/README.md b/examples/user-management/solid-user-management/README.md index e35bd826d2d..6f51f9a0182 100644 --- a/examples/user-management/solid-user-management/README.md +++ b/examples/user-management/solid-user-management/README.md @@ -59,7 +59,7 @@ Run the application: `npm run dev`. Open your browser to `https://localhost:3000 ### Postgres Row level security -This project uses very high-level Authorization using Postgres' Role Level Security. +This project uses very high-level Authorization using Postgres' Row Level Security. When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions. When a user logs in, they are issued a JWT with the role `authenticated` and their UUID. We can use these details to provide fine-grained control over what each user can and cannot do. diff --git a/examples/user-management/svelte-user-management/README.md b/examples/user-management/svelte-user-management/README.md index 38474c80339..a0de424be41 100644 --- a/examples/user-management/svelte-user-management/README.md +++ b/examples/user-management/svelte-user-management/README.md @@ -57,7 +57,7 @@ Run the application: `npm run dev`. Open your browser to `https://localhost:5173 ### Postgres Row level security -This project uses very high-level Authorization using Postgres' Role Level Security. +This project uses very high-level Authorization using Postgres' Row Level Security. When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions. When a user logs in, they are issued a JWT with the role `authenticated` and their UUID. We can use these details to provide fine-grained control over what each user can and cannot do. diff --git a/examples/user-management/sveltekit-user-management/README.md b/examples/user-management/sveltekit-user-management/README.md index fb147469024..448f7eb97a9 100644 --- a/examples/user-management/sveltekit-user-management/README.md +++ b/examples/user-management/sveltekit-user-management/README.md @@ -32,7 +32,7 @@ Run the application: `npm run dev`. Open your browser to `https://localhost:5173 ### Postgres Row level security -This project uses very high-level Authorization using Postgres' Role Level Security. +This project uses very high-level Authorization using Postgres' Row Level Security. When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions. When a user logs in, they are issued a JWT with the role `authenticated` and their UUID. We can use these details to provide fine-grained control over what each user can and cannot do.