diff --git a/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts b/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts
index 397a76cdfb1..2d8ba45fab2 100644
--- a/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts
+++ b/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts
@@ -576,6 +576,7 @@ export const auth = {
{ name: 'Managing User Data', url: '/guides/auth/managing-user-data' },
{ name: 'Multi-Factor Authentication', url: '/guides/auth/auth-mfa' },
{ name: 'Row Level Security', url: '/guides/auth/row-level-security' },
+ { name: 'Column Level Security', url: '/guides/auth/column-level-security' },
],
},
{
diff --git a/apps/docs/pages/guides/auth/column-level-security.mdx b/apps/docs/pages/guides/auth/column-level-security.mdx
new file mode 100644
index 00000000000..e5c22dd79d2
--- /dev/null
+++ b/apps/docs/pages/guides/auth/column-level-security.mdx
@@ -0,0 +1,158 @@
+import Layout from '~/layouts/DefaultGuideLayout'
+
+export const meta = {
+ id: 'column-level-security',
+ title: 'Column Level Security',
+ description: 'Secure your data using Postgres Column Level Security.',
+}
+
+PostgreSQL's [Row Level Security (RLS)](https://www.postgresql.org/docs/current/ddl-rowsecurity.html) gives you granular control over who can access rows of data. However, it doesn't give you control over which columns they can access within rows. Sometimes you want to restrict access to specific columns in your database. Column Level Privileges allows you to do just that.
+
+
+ This is an advanced feature. We do not recommend using column-level privileges for most users.
+ Instead, we recommend using RLS policies in combination with a dedicated table for handling user
+ roles.
+
+
+## Policies at the Row Level
+
+Policies in Row Level Security (RLS) are used to restrict access to rows in a table. Think of them like adding a `WHERE` clause to every query.
+
+For example, let's assume you have a `posts` table with the following columns:
+
+- `id`
+- `user_id`
+- `title`
+- `content`
+- `created_at`
+- `updated_at`
+
+You can restrict updates to just the user who created it using [RLS](/docs/guides/auth#row-level-security), with the following policy:
+
+```sql
+create a policy "Allow update for owners" on posts for
+update
+ using (auth.uid () = user_id);
+```
+
+However, this gives the post owner full access to update the row, including all of the columns.
+
+## Privileges at the Column Level
+
+To restrict access to columns, you can use [Privileges](https://www.postgresql.org/docs/current/ddl-priv.html).
+
+There are two types of privileges in PostgreSQL:
+
+1. **table-level**: Grants the privilege on all columns in the table.
+2. **column-level** Grants the privilege on a specific column in the table.
+
+You can have both types of privileges on the same table. If you have both, and you revoke the column-level privilege, the table-level privilege will still be in effect.
+
+By default, our table will have a table-level `UPDATE` privilege, which means that the `authenticated` role can update all the columns in the table.
+
+```sql
+revoke
+update
+ on table public.posts
+from
+ authenticated;
+
+grant
+update
+ (title, content) on table public.posts to authenticated;
+```
+
+In the above example, we are revoking the table-level `UPDATE` privilege from the `authenticated` role and granting a column-level `UPDATE` privilege on just the `title` and `content` columns.
+
+If we want to restrict access to updating the `title` column:
+
+```sql
+revoke
+update
+ (title) on table public.posts
+from
+ authenticated;
+```
+
+This time, we are revoking the column-level `UPDATE` privilege of the `title` column from the `authenticated` role. We didn't need to revoke the table-level `UPDATE` privilege because it's already revoked.
+
+## Manage column privileges in the Dashboard
+
+You can view and edit the privileges in the [Supabase Studio](https://app.supabase.com/project/_/auth/privileges).
+
+
+
+## Manage column privileges in Migrations
+
+While you can manage privileges directly from the Dashboard, as your project grows you may want to manage them in your migrations. Read about database migrations in the [Local Development](https://supabase.com/docs/guides/getting-started/local-development#database-migrations) guide.
+
+
+
+
+
+
+ To get started, generate a [new migration](https://supabase.com/docs/reference/cli/supabase-migration-new) to store the SQL needed to create your table along with row and column-level privileges.
+
+
+
+
+
+```bash
+supabase migration new create_posts_table
+```
+
+
+
+
+
+
+
+
+
+
+ This creates a new migration: supabase/migrations/\
+ _create_posts_table.sql.
+
+ To that file, add the SQL to create this `posts` table with row and column-level privileges.
+
+
+
+ ```sql
+
+create table
+posts (
+id bigint primary key generated always as identity,
+user_id text,
+title text,
+content text,
+created_at timestamptz default now()
+updated_at timestamptz default now()
+);
+
+-- Add row-level security
+create a policy "Allow update for owners" on posts for
+update
+using (auth.uid () = user_id);
+
+-- Add column-level security
+revoke
+update
+(title) on table public.posts
+from
+authenticated;
+
+```
+
+
+
+
+
+
+## Considerations when using column-level privileges
+- If you turn off a column privilege you won't be able to use that column at all.
+- All operations (insert, update, delete) as well as using `select *` will fail.
+
+
+export const Page = ({ children }) =>
+
+export default Page
diff --git a/apps/docs/public/img/guides/privileges/column-level-privileges.png b/apps/docs/public/img/guides/privileges/column-level-privileges.png
new file mode 100644
index 00000000000..6de359627ca
Binary files /dev/null and b/apps/docs/public/img/guides/privileges/column-level-privileges.png differ
diff --git a/apps/studio/components/interfaces/App/FeaturePreview/CLSPreview.tsx b/apps/studio/components/interfaces/App/FeaturePreview/CLSPreview.tsx
new file mode 100644
index 00000000000..facc947af55
--- /dev/null
+++ b/apps/studio/components/interfaces/App/FeaturePreview/CLSPreview.tsx
@@ -0,0 +1,56 @@
+import { useParams } from 'common'
+import { Markdown } from 'components/interfaces/Markdown'
+import { BASE_PATH } from 'lib/constants'
+import Image from 'next/image'
+import { AlertDescription_Shadcn_, AlertTitle_Shadcn_, Alert_Shadcn_, IconAlertCircle } from 'ui'
+
+const CLSPreview = () => {
+ const { ref } = useParams()
+
+ return (
+
+
+
+
+
+
+
+ Changes to column privileges will not be reflected in migrations when running{' '}
+ supabase db diff.
+
+
+ Column privileges are not supported in the current version of the Supabase CLI.
+
+ You will need to manually apply these changes to your database.
+
+
+
+
+ {isEnabled ? (
+ <>
+ {!diffWarningDismissed && (
+
+
+
+ Changes to column privileges will not be reflected in migrations when running{' '}
+ supabase db diff.
+
+
+ Column privileges are not supported in the current version of the Supabase CLI.
+
+ You will need to manually apply these changes to your database.
+
+
+
+ )}
+
+ {!selectStarWarningDismissed && (
+
+
+
+ Changing column privileges can break existing queries.
+
+
+ If you remove a column privilege for a role, that role will lose all access to
+ that column.
+
+ All operations selecting * (including{' '}
+ returning * for{' '}
+ insert, update
+ , and delete) will fail.
+
+
+
+ )}
+
+
+ {isLocked && (
+
+ )}
+ {isLoading ? (
+
+ ) : isError ? (
+
+ ) : table && tablePrivilege ? (
+
+
+
+ ) : (tables ?? []).length === 0 ? (
+
+
There are no tables in the {selectedSchema} schema
+
+ Once a table is available in the schema, you may manage it's column-level
+ privileges here
+
+ {selectedSchema === 'public' && (
+
+ )}
+
+ ) : (
+
+
Select a table to edit privileges
+
+ )}
+
+ ) : (
+
+
+ Column-level privileges is a dashboard feature preview
+
+
+ You may access this feature by enabling it under dashboard feature previews.
+
+