From 19cf4bb4bfb98d85ffe028b049a188b74705912c Mon Sep 17 00:00:00 2001
From: Danny White <3104761+dnywh@users.noreply.github.com>
Date: Mon, 26 Jan 2026 17:41:05 +1000
Subject: [PATCH] feat(studio): consolidate settings phase 2 (#37612)
* new slugs
* remove symlinks
* rabbit
---
.../guides/auth/general-configuration.mdx | 2 +-
.../guides/functions/examples/send-emails.mdx | 2 +-
.../docs/content/guides/functions/secrets.mdx | 2 +-
...-or-invalid-scram-server-final-message.mdx | 2 +-
apps/docs/spec/supabase_dart_v2.yml | 6 +--
apps/docs/spec/supabase_js_v2.yml | 6 +--
apps/docs/spec/supabase_kt_v2.yml | 4 +-
apps/docs/spec/supabase_kt_v3.yml | 4 +-
apps/docs/spec/supabase_py_v2.yml | 6 +--
apps/docs/spec/supabase_swift_v2.yml | 6 +--
.../SettingsMenu.utils.tsx | 48 -------------------
apps/studio/next.config.js | 4 +-
.../2023-10-04-beta-update-september-2023.mdx | 2 +-
...4-supabase-auth-identity-linking-hooks.mdx | 4 +-
.../_blog/2024-04-17-anonymous-sign-ins.mdx | 4 +-
examples/auth/hono-full/README.md | 2 +-
16 files changed, 28 insertions(+), 76 deletions(-)
diff --git a/apps/docs/content/guides/auth/general-configuration.mdx b/apps/docs/content/guides/auth/general-configuration.mdx
index 35b9f5ca69e..9a576119fab 100644
--- a/apps/docs/content/guides/auth/general-configuration.mdx
+++ b/apps/docs/content/guides/auth/general-configuration.mdx
@@ -20,7 +20,7 @@ This section covers the [general configuration options](/dashboard/project/_/aut
- [Audit Logs (BETA)](/dashboard/project/_/auth/audit-logs) to track and monitor auth events in your project.
- [Performance](/dashboard/project/_/auth/performance) to configure and optimize authentication server settings.
-Supabase Auth provides these [general configuration options](/dashboard/project/_/settings/auth) to control user access to your application:
+Supabase Auth provides these [general configuration options](/dashboard/project/_/auth/providers) to control user access to your application:
- **Allow new users to sign up**: Users will be able to sign up. If this config is disabled, only existing users can sign in.
diff --git a/apps/docs/content/guides/functions/examples/send-emails.mdx b/apps/docs/content/guides/functions/examples/send-emails.mdx
index 7b4ce506d19..60fc7926ad5 100644
--- a/apps/docs/content/guides/functions/examples/send-emails.mdx
+++ b/apps/docs/content/guides/functions/examples/send-emails.mdx
@@ -79,7 +79,7 @@ supabase functions deploy resend --no-verify-jwt
-When you deploy to Supabase, make sure that your `RESEND_API_KEY` is set in [Edge Function Secrets Management](/dashboard/project/_/settings/functions)
+When you deploy to Supabase, make sure that your `RESEND_API_KEY` is set in [Edge Function Secrets Management](/dashboard/project/_/functions/secrets)
diff --git a/apps/docs/content/guides/functions/secrets.mdx b/apps/docs/content/guides/functions/secrets.mdx
index 9fd3aadc306..f8d2cf6ebd8 100644
--- a/apps/docs/content/guides/functions/secrets.mdx
+++ b/apps/docs/content/guides/functions/secrets.mdx
@@ -95,7 +95,7 @@ You will also need to set secrets for your production Edge Functions. You can do
**Using the Dashboard**:
-1. Visit [Edge Function Secrets Management](/dashboard/project/_/settings/functions) page in your Dashboard.
+1. Visit [Edge Function Secrets Management](/dashboard/project/_/functions/secrets) page in your Dashboard.
2. Add the Key and Value for your secret and press Save
,
- },
- ...(authEnabled
- ? [
- {
- name: 'Authentication',
- key: 'auth',
- url: authProvidersEnabled
- ? `/project/${ref}/auth/providers`
- : `/project/${ref}/auth/policies`,
- items: [],
- rightIcon: ,
- },
- ]
- : []),
- ...(storageEnabled
- ? [
- {
- name: 'Storage',
- key: 'storage',
- url: `/project/${ref}/storage/settings`,
- items: [],
- rightIcon: ,
- },
- ]
- : []),
- ...(edgeFunctionsEnabled
- ? [
- {
- name: 'Edge Functions',
- key: 'functions',
- url: `/project/${ref}/functions/secrets`,
- items: [],
- rightIcon: ,
- },
- ]
- : []),
- ],
- },
-
{
title: 'Billing',
items: [
diff --git a/apps/studio/next.config.js b/apps/studio/next.config.js
index d49a79c513f..29599dc5d51 100644
--- a/apps/studio/next.config.js
+++ b/apps/studio/next.config.js
@@ -436,8 +436,8 @@ const nextConfig = {
},
{
source: '/project/:ref/settings/auth',
- destination: '/project/:ref/auth',
- permanent: false,
+ destination: '/project/:ref/auth/providers',
+ permanent: true,
},
...(process.env.NEXT_PUBLIC_BASE_PATH?.length
diff --git a/apps/www/_blog/2023-10-04-beta-update-september-2023.mdx b/apps/www/_blog/2023-10-04-beta-update-september-2023.mdx
index 95fed1db603..c2f11db94af 100644
--- a/apps/www/_blog/2023-10-04-beta-update-september-2023.mdx
+++ b/apps/www/_blog/2023-10-04-beta-update-september-2023.mdx
@@ -78,7 +78,7 @@ Added HNSW support inside Vecs, our Python library for `pgvector`. Vecs automati
- [PostgREST] JWT caching just landed. API requests are about to get 100ms faster. [[PR](https://github.com/PostgREST/postgrest/pull/2928)]
- [Auth] Added a default in-memory storage mechanism to allow using `supabase-js` in these environments to fall back to use this default storage mechanism now. Upgrade to supabase-js v2.36.0 or gotrue-js v2.54.0 for the latest changes. [[PR](https://github.com/supabase/gotrue-js/pull/774)]
- [Edge Functions] Supports much simpler API for creating functions `Deno.serve(req => new Response("ok"))`. No `http` standard library dependency needed. (Thanks eifr for contributing with updated CLI templates. [[PR](https://github.com/supabase/cli/pull/1504)]
-- [Edge Functions] You can manage the secrets for your project's Edge Functions via the dashboard. [[Try it now](https://supabase.com/dashboard/project/_/settings/functions)]
+- [Edge Functions] You can manage the secrets for your project's Edge Functions via the dashboard. [[Try it now](https://supabase.com/dashboard/project/_/functions/secrets)]
## Supabase at the AI Engineer Summit
diff --git a/apps/www/_blog/2023-12-14-supabase-auth-identity-linking-hooks.mdx b/apps/www/_blog/2023-12-14-supabase-auth-identity-linking-hooks.mdx
index a3345b21d90..06cad16ee19 100644
--- a/apps/www/_blog/2023-12-14-supabase-auth-identity-linking-hooks.mdx
+++ b/apps/www/_blog/2023-12-14-supabase-auth-identity-linking-hooks.mdx
@@ -62,7 +62,7 @@ const { data, error } = await supabase.auth.unlinkIdentity(googleIdentity)
Currently, these methods support linking an OAuth identity. To link an email or phone identity to the user, you can use the [`updateUser()`](/docs/reference/javascript/auth-updateuser)method.
-Manual linking is disabled by default. You can enable it for your project in [the dashboard Auth settings](/dashboard/project/_/settings/auth).
+Manual linking is disabled by default. You can enable it for your project in [the dashboard Auth settings](/dashboard/project/_/auth/providers).
-As an additional step, we have added the ability to specify password requirements for your users. This can be configured from your project’s Auth settings in [the dashboard](/dashboard/project/_/settings/auth):
+As an additional step, we have added the ability to specify password requirements for your users. This can be configured from your project’s Auth settings in [the dashboard](/dashboard/project/_/auth/providers):
![Adding password requirements]()