diff --git a/installation/authentication-setup/supabase-auth.mdx b/installation/authentication-setup/supabase-auth.mdx
index a852f123..e4faed15 100644
--- a/installation/authentication-setup/supabase-auth.mdx
+++ b/installation/authentication-setup/supabase-auth.mdx
@@ -17,6 +17,10 @@ You can implement various types of auth:
    * [Example](https://github.com/powersync-ja/powersync-jwks-example/)
 * Experimental: We've also heard from the community that Supabase's newly released [support for external auth providers works](https://supabase.com/blog/third-party-auth-mfa-phone-send-hooks), but we don't have any examples for this yet.
 
+<Note>
+The "Supabase Auth" setting no longer works for Supabase projects created after 25 November 2024. While we are working with Supabase on a fix, please apply this workaround: https://releases.powersync.com/announcements/important-notice-for-supabase-users-using-supabase-jwts
+</Note>
+
 To implement either Supabase Auth or Anonymous Sign-Ins, enable the "Use Supabase Auth" setting on the PowerSync instance. (This is also [covered in the Supabase & PowerSync integration guide](/integration-guides/supabase-+-powersync#configuring-powersync))
 
 Internally, Supabase auth signs the token using HS256, using a secret available as `current_setting('app.settings.jwt_secret')` on the database.
diff --git a/installation/database-connection.mdx b/installation/database-connection.mdx
index 08fef6a9..fc84e80a 100644
--- a/installation/database-connection.mdx
+++ b/installation/database-connection.mdx
@@ -38,6 +38,10 @@ Select your Postgres hosting provider for steps to connect your Postgres databas
 2. Under the **"Client Auth"** tab, enable **"Use Supabase Auth".**
 3. Click **"Save".**
 
+<Note>
+The "Supabase Auth" setting no longer works for Supabase projects created after 25 November 2024. While we are working with Supabase on a fix, please apply this workaround: https://releases.powersync.com/announcements/important-notice-for-supabase-users-using-supabase-jwts
+</Note>
+
 PowerSync deploys and configures an isolated cloud environment for you, which can take a few minutes to complete.
 
 ### Troubleshooting
diff --git a/integration-guides/flutterflow-+-powersync.mdx b/integration-guides/flutterflow-+-powersync.mdx
index e94fec6d..2ceedf33 100644
--- a/integration-guides/flutterflow-+-powersync.mdx
+++ b/integration-guides/flutterflow-+-powersync.mdx
@@ -100,6 +100,10 @@ It is important to uncheck this checkbox
 2. Under the **"Client Auth"** tab, enable **"Use Supabase Auth".**
 3. Click **"Save".**
 
+<Note>
+The "Supabase Auth" setting no longer works for Supabase projects created after 25 November 2024. While we are working with Supabase on a fix, please apply this workaround: https://releases.powersync.com/announcements/important-notice-for-supabase-users-using-supabase-jwts
+</Note>
+
 PowerSync deploys and configures an isolated cloud environment for you, which will take a few minutes to complete.
 
 ### Configure Sync Rules
diff --git a/integration-guides/supabase-+-powersync.mdx b/integration-guides/supabase-+-powersync.mdx
index ad8c95a4..5826582d 100644
--- a/integration-guides/supabase-+-powersync.mdx
+++ b/integration-guides/supabase-+-powersync.mdx
@@ -138,6 +138,10 @@ It is important to uncheck this checkbox
 </Frame>
 8. Click **"Save".**
 
+<Note>
+The "Supabase Auth" setting no longer works for Supabase projects created after 25 November 2024. While we are working with Supabase on a fix, please apply this workaround: https://releases.powersync.com/announcements/important-notice-for-supabase-users-using-supabase-jwts
+</Note>
+
 PowerSync deploys and configures an isolated cloud environment for you, which will take a few minutes to complete.
 
 ### Configure Sync Rules