Skip to content

The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.

docs: add cross-links to related guides (part 3) (#51858)

Kody Jackson004d90c5a36f
diff --git a/apps/docs/content/guides/self-hosting/self-hosted-s3.mdx b/apps/docs/content/guides/self-hosting/self-hosted-s3.mdx
index 48e85495b3d..5f79b28f68b 100644
--- a/apps/docs/content/guides/self-hosting/self-hosted-s3.mdx
+++ b/apps/docs/content/guides/self-hosting/self-hosted-s3.mdx
@@ -148,7 +148,7 @@ storage:
You can authenticate to Supabase's S3-compatible storage using a user’s JWT to enforce Row-Level Security (RLS) across S3 operations. This is useful when initializing the S3 client on the server for a specific user session, or when using the client directly from the frontend.
-All operations performed with a session token are scoped to the authenticated user, and any RLS policies defined in the storage schema will be applied.
+All operations performed with a session token are scoped to the authenticated user, and any RLS policies defined in the [storage schema](/docs/guides/storage/schema/design) will be applied.
To authenticate with S3 using a session token, provide the following credentials:
diff --git a/apps/docs/content/guides/storage.mdx b/apps/docs/content/guides/storage.mdx
index f68c79f88c6..d5330f429b7 100644
--- a/apps/docs/content/guides/storage.mdx
+++ b/apps/docs/content/guides/storage.mdx
@@ -12,7 +12,7 @@ Supabase Storage is a robust, scalable solution for managing files of any size w
## Key features
-- **Multi Protocol** - S3 compatible Storage, RESTful API, TUS resumable uploads
+- **Multi Protocol** - S3 compatible Storage, RESTful API, TUS [resumable uploads](/docs/guides/storage/uploads/resumable-uploads)
- **Global CDN** - Serve your assets with lightning-fast performance from over 285 cities worldwide
- **Image Optimization** - Resize, compress, and transform media files on the fly with built-in image processing
- **Fine-grained Access Control** - Manage file permissions with row-level security and custom policies
diff --git a/apps/docs/content/guides/storage/analytics/connecting-to-analytics-bucket.mdx b/apps/docs/content/guides/storage/analytics/connecting-to-analytics-bucket.mdx
index 0d6be1314ab..18dd1fbea51 100644
--- a/apps/docs/content/guides/storage/analytics/connecting-to-analytics-bucket.mdx
+++ b/apps/docs/content/guides/storage/analytics/connecting-to-analytics-bucket.mdx
@@ -8,7 +8,7 @@ Expect rapid changes, limited features, and possible breaking updates. [Share fe
</Admonition>
-Analytics buckets require authentication with two distinct services:
+[Analytics buckets](/docs/guides/storage/analytics/introduction) require authentication with two distinct services:
## Architecture overview
diff --git a/apps/docs/content/guides/storage/management/download-objects.mdx b/apps/docs/content/guides/storage/management/download-objects.mdx
index 3bd05d01748..98ce2f1908b 100644
--- a/apps/docs/content/guides/storage/management/download-objects.mdx
+++ b/apps/docs/content/guides/storage/management/download-objects.mdx
@@ -14,7 +14,7 @@ You can download individual files directly from the [**Storage > Files**](/dashb
## Using the Supabase CLI
-You can use the `supabase storage` commands to list and copy objects from your linked project.
+You can use the `supabase storage` commands to list and [copy objects](/docs/guides/storage/management/copy-move-objects) from your linked project.
See the [CLI reference](/docs/reference/cli/supabase-storage) for available commands.
diff --git a/apps/docs/content/guides/storage/s3/authentication.mdx b/apps/docs/content/guides/storage/s3/authentication.mdx
index 294e0b24c53..0fc05bcbe65 100644
--- a/apps/docs/content/guides/storage/s3/authentication.mdx
+++ b/apps/docs/content/guides/storage/s3/authentication.mdx
@@ -88,7 +88,7 @@ On [local development](/docs/guides/local-development), use these values:
You can authenticate to Supabase S3 with a user JWT token to provide limited access via RLS to all S3 operations. This is useful when you want initialize the S3 client on the server scoped to a specific user, or use the S3 client directly from the client side.
-All S3 operations performed with the Session Token are scoped to the authenticated user. RLS policies on the Storage Schema are respected.
+All S3 operations performed with the Session Token are scoped to the authenticated user. RLS policies on the [Storage Schema](/docs/guides/storage/schema/design) are respected.
To authenticate with S3 using a Session Token, use the following credentials:
diff --git a/apps/docs/content/guides/storage/security/ownership.mdx b/apps/docs/content/guides/storage/security/ownership.mdx
index dd0d6aa8ae2..321a4c3c71a 100644
--- a/apps/docs/content/guides/storage/security/ownership.mdx
+++ b/apps/docs/content/guides/storage/security/ownership.mdx
@@ -16,7 +16,7 @@ When using the `service_key` to create a resource, the owner will not be set and
<Admonition type="note">
-The Storage schema has 2 fields to represent ownership: `owner` and `owner_id`. `owner` is deprecated and will be removed. Use `owner_id` instead.
+The [Storage schema](/docs/guides/storage/schema/design) has 2 fields to represent ownership: `owner` and `owner_id`. `owner` is deprecated and will be removed. Use `owner_id` instead.
</Admonition>
diff --git a/apps/docs/content/guides/storage/vector/introduction.mdx b/apps/docs/content/guides/storage/vector/introduction.mdx
index 124fce369fa..e32854d2120 100644
--- a/apps/docs/content/guides/storage/vector/introduction.mdx
+++ b/apps/docs/content/guides/storage/vector/introduction.mdx
@@ -9,7 +9,7 @@ Expect rapid changes, limited features, and possible breaking updates. [Share fe
</Admonition>
-Vector buckets enable efficient storage and similarity search of vector embeddings. Built on S3-compatible storage, they provide high-performance semantic search capabilities for AI and machine learning applications.
+Vector buckets enable efficient storage and similarity search of vector embeddings. Built on S3-compatible storage, they provide high-performance [semantic search](/docs/guides/ai/semantic-search) capabilities for AI and machine learning applications.
## What are Vector buckets?
diff --git a/apps/docs/content/troubleshooting/auth-hooks-invalid-payload-when-anonymous-users-attempt-phone-changes-022c47.mdx b/apps/docs/content/troubleshooting/auth-hooks-invalid-payload-when-anonymous-users-attempt-phone-changes-022c47.mdx
index dc0918ea468..cd06d14e276 100644
--- a/apps/docs/content/troubleshooting/auth-hooks-invalid-payload-when-anonymous-users-attempt-phone-changes-022c47.mdx
+++ b/apps/docs/content/troubleshooting/auth-hooks-invalid-payload-when-anonymous-users-attempt-phone-changes-022c47.mdx
@@ -9,7 +9,7 @@ http_status_code = 500
message = "Invalid payload sent to hook"
---
-An 'Invalid payload sent to hook' error (500) occurs in Auth hooks when the payload includes `new_phone` for an anonymous user.
+An 'Invalid payload sent to hook' error (500) occurs in [Auth hooks](/docs/guides/auth/auth-hooks) when the payload includes `new_phone` for an anonymous user.
## Why does this happen?
diff --git a/apps/docs/content/troubleshooting/change-project-region-eWJo5Z.mdx b/apps/docs/content/troubleshooting/change-project-region-eWJo5Z.mdx
index 757b90d1e27..990b5ff1b26 100644
--- a/apps/docs/content/troubleshooting/change-project-region-eWJo5Z.mdx
+++ b/apps/docs/content/troubleshooting/change-project-region-eWJo5Z.mdx
@@ -11,4 +11,4 @@ Each Supabase project is provisioned on hardware in the chosen region, so it is
Therefore, the process to change the region of a Supabase Project is to create a new project in the desired region and migrate your existing project using the [migrations guide](/docs/guides/platform/migrating-within-supabase).
-If you are using third-party auth(Facebook, Google, etc.), you need to manually copy over your client id/secret pairs in the dashboard. Also, you'd need to change your API URL/Anon or Service Keys, which is usually done via ENV vars on your web host.
+If you are using [third-party auth](/docs/guides/auth/social-login)(Facebook, Google, etc.), you need to manually copy over your client id/secret pairs in the dashboard. Also, you'd need to change your API URL/Anon or Service Keys, which is usually done via ENV vars on your web host.
diff --git a/apps/docs/content/troubleshooting/database-api-42501-errors.mdx b/apps/docs/content/troubleshooting/database-api-42501-errors.mdx
index 4e8a84cd550..02093f97171 100644
--- a/apps/docs/content/troubleshooting/database-api-42501-errors.mdx
+++ b/apps/docs/content/troubleshooting/database-api-42501-errors.mdx
@@ -37,7 +37,7 @@ They tend to be caused by one of the following factors.
## Attempted to access a forbidden schema
-API roles cannot access certain schemas, most notably `auth` and `vault`. This restriction extends to Foreign Data Wrappers relying on `vault`. While you can bypass it using a [security definer function](/docs/guides/database/functions?queryGroups=language&language=sql&queryGroups=example-view&example-view=sql#security-definer-vs-invoker), these schemas are intentionally restricted for security reasons.
+API roles cannot access certain schemas, most notably `auth` and `vault`. This restriction extends to [Foreign Data Wrappers](/docs/guides/database/extensions/wrappers/overview) relying on `vault`. While you can bypass it using a [security definer function](/docs/guides/database/functions?queryGroups=language&language=sql&queryGroups=example-view&example-view=sql#security-definer-vs-invoker), these schemas are intentionally restricted for security reasons.
## Attempted to access a custom schema
diff --git a/apps/docs/content/troubleshooting/edge-function-shutdown-reasons-explained.mdx b/apps/docs/content/troubleshooting/edge-function-shutdown-reasons-explained.mdx
index 2614ec2d724..2cc38c69a13 100644
--- a/apps/docs/content/troubleshooting/edge-function-shutdown-reasons-explained.mdx
+++ b/apps/docs/content/troubleshooting/edge-function-shutdown-reasons-explained.mdx
@@ -92,7 +92,7 @@ These events are surfaced through logs and observability tools, allowing you to
- If you're seeing `EarlyDrop` but expected more work to happen, check for:
- Promises that weren't properly awaited
- Event listeners or timers that weren't cleaned up
- - Background tasks that should have completed but didn't
+ - [Background tasks](/docs/guides/functions/background-tasks) that should have completed but didn't
- If you intentionally have background work that should continue after the response, make sure those promises are awaited before the function returns
### TerminationRequested
diff --git a/apps/docs/content/troubleshooting/email-password-login-disabled-supabase-vercel-marketplace-a7dd36.mdx b/apps/docs/content/troubleshooting/email-password-login-disabled-supabase-vercel-marketplace-a7dd36.mdx
index 4684ead253f..a46d2fed5ae 100644
--- a/apps/docs/content/troubleshooting/email-password-login-disabled-supabase-vercel-marketplace-a7dd36.mdx
+++ b/apps/docs/content/troubleshooting/email-password-login-disabled-supabase-vercel-marketplace-a7dd36.mdx
@@ -5,7 +5,7 @@ keywords = [ "Vercel"]
database_id = "f988e832-b0c3-4b30-8e20-8d5854943b32"
---
-If your Supabase account was initiated via the Vercel Marketplace, you will not be able to log in directly using email/password or reset your password. This is because such accounts are tightly coupled to Vercel's authentication system, restricting login to Vercel's integrated methods.
+If your Supabase account was initiated via the [Vercel Marketplace](/docs/guides/integrations/vercel-marketplace), you will not be able to log in directly using email/password or reset your password. This is because such accounts are tightly coupled to Vercel's authentication system, restricting login to Vercel's integrated methods.
To access your Supabase account independently of the Vercel Marketplace, you can use GitHub OAuth as an alternative:
diff --git a/apps/docs/content/troubleshooting/error-invalid-byte-sequence-for-encoding-utf8-0x00-when-accessing-triggers-or-webhooks-e78cf8.mdx b/apps/docs/content/troubleshooting/error-invalid-byte-sequence-for-encoding-utf8-0x00-when-accessing-triggers-or-webhooks-e78cf8.mdx
index 71907b1b655..aec8b7e1c03 100644
--- a/apps/docs/content/troubleshooting/error-invalid-byte-sequence-for-encoding-utf8-0x00-when-accessing-triggers-or-webhooks-e78cf8.mdx
+++ b/apps/docs/content/troubleshooting/error-invalid-byte-sequence-for-encoding-utf8-0x00-when-accessing-triggers-or-webhooks-e78cf8.mdx
@@ -11,7 +11,7 @@ This setting, when `off`, can cause issues with how certain character sequences
To resolve this issue:
-1. Connect to your database instance using the [SQL Editor](/dashboard/project/_/sql/new) in the Dashboard or a client like `psql`.
+1. [Connect to your database](/docs/guides/database/connecting-to-postgres) instance using the [SQL Editor](/dashboard/project/_/sql/new) in the Dashboard or a client like `psql`.
2. Execute the following SQL command:
```sql
ALTER DATABASE postgres SET standard_conforming_strings = on;
diff --git a/apps/docs/content/troubleshooting/error-target-organization-is-not-managed-by-vercel-marketplace-during-project-transfer-5262c3.mdx b/apps/docs/content/troubleshooting/error-target-organization-is-not-managed-by-vercel-marketplace-during-project-transfer-5262c3.mdx
index bee1e46a14e..306aaca1a98 100644
--- a/apps/docs/content/troubleshooting/error-target-organization-is-not-managed-by-vercel-marketplace-during-project-transfer-5262c3.mdx
+++ b/apps/docs/content/troubleshooting/error-target-organization-is-not-managed-by-vercel-marketplace-during-project-transfer-5262c3.mdx
@@ -8,7 +8,7 @@ database_id = "6083c9eb-b9fc-4d19-bc64-bb4b7efeecdd"
If you encounter the error "Target organization is not managed by Vercel Marketplace (currently unsupported)" when attempting a project transfer, it indicates an attempt to move a project from a Supabase-managed organization to a Vercel Marketplace-managed organization. This transfer direction is currently not supported due to existing Vercel Marketplace API limitations.
**Supported Transfer Direction:**
-Project transfers from a Vercel-managed organization to a Supabase-managed organization are supported. To perform this transfer:
+[Project transfers](/docs/guides/platform/project-transfer) from a Vercel-managed organization to a Supabase-managed organization are supported. To perform this transfer:
1. Create a new Supabase-managed organization via your [dashboard](/dashboard).
2. From your project settings, initiate a transfer to the newly created Supabase-managed organization.
diff --git a/apps/docs/content/troubleshooting/fatal-password-authentication-failed.mdx b/apps/docs/content/troubleshooting/fatal-password-authentication-failed.mdx
index 830c24e43a1..c7c6890a336 100644
--- a/apps/docs/content/troubleshooting/fatal-password-authentication-failed.mdx
+++ b/apps/docs/content/troubleshooting/fatal-password-authentication-failed.mdx
@@ -30,7 +30,7 @@ If you're connecting through the shared pooler and this started right after rese
## Using a custom role
-Custom Postgres roles with `LOGIN` are supported. They work on direct connections, the dedicated pooler, and the shared Supavisor pooler. You do not register a role with the pooler as a separate step. The pooler reads the role's credentials from Postgres on demand, so creating the role in the database is all that is needed.
+[Custom Postgres roles](/docs/guides/database/postgres/roles) with `LOGIN` are supported. They work on direct connections, the dedicated pooler, and the shared Supavisor pooler. You do not register a role with the pooler as a separate step. The pooler reads the role's credentials from Postgres on demand, so creating the role in the database is all that is needed.
If you reset the password of a custom role while using the shared pooler (Supavisor), a pooled connection can still fail with `FATAL: password authentication failed` (SQLSTATE `28P01`) even when the new password is correct. The pooler may still use cached credentials briefly. Confirm the new password with a direct connection, then retry through Supavisor with bounded retries. Direct connections and the dedicated pooler are not affected by this cache behavior.
diff --git a/apps/docs/content/troubleshooting/how-to-bypass-cooldown-period.mdx b/apps/docs/content/troubleshooting/how-to-bypass-cooldown-period.mdx
index 53d114e7db5..a1b33febab5 100644
--- a/apps/docs/content/troubleshooting/how-to-bypass-cooldown-period.mdx
+++ b/apps/docs/content/troubleshooting/how-to-bypass-cooldown-period.mdx
@@ -11,7 +11,7 @@ See the [**AWS docs**](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/AP
There are a few options to work around the cooldown, depending on the state of your database:
-1. **Restore to a new project**: This spins up a new instance with a new disk, bypassing the cooldown entirely. It’s a great option if you're okay with a new project and project refactoring. [**Docs: restoring to a new project**](/docs/guides/platform/backups#restore-to-a-new-project).
+1. **[Restore to a new project](/docs/guides/platform/clone-project)**: This spins up a new instance with a new disk, bypassing the cooldown entirely. It’s a great option if you're okay with a new project and project refactoring. [**Docs: restoring to a new project**](/docs/guides/platform/backups#restore-to-a-new-project).
2. **pg_upgrade**: Our [**pg_upgrade**](/docs/guides/platform/upgrading) implementation migrates your data to a new disk, which skips the cooldown. The main requirement here is that the database must be operational - pg_upgrade can't run if your database is in a degraded or inaccessible state.
3. **Pause and Restore**: This also migrates to a new disk but is only available for projects on the Free plan. If you're not on the Free plan, you'd need to [**transfer your project to an organization on the Free plan**](/docs/guides/platform/project-transfer) first.
diff --git a/apps/docs/content/troubleshooting/not-receiving-auth-emails-from-the-supabase-project-OFSNzw.mdx b/apps/docs/content/troubleshooting/not-receiving-auth-emails-from-the-supabase-project-OFSNzw.mdx
index 9f6258ae9d1..d25c8667e8b 100644
--- a/apps/docs/content/troubleshooting/not-receiving-auth-emails-from-the-supabase-project-OFSNzw.mdx
+++ b/apps/docs/content/troubleshooting/not-receiving-auth-emails-from-the-supabase-project-OFSNzw.mdx
@@ -7,7 +7,7 @@ keywords = [ "smtp", "email", "delivery", "logs", "provider", "firewalls" ]
database_id = "98e3b318-ad9a-41f5-ada0-44b61970ab4f"
---
-**We strongly recommend configuring your own custom SMTP provider** in your projects to avoid running into issues with sending emails from your project. The built-in email provider is for demonstration purposes only and offers a very low rate limit. You can read more details about the rate limits [here](/docs/guides/deployment/going-into-prod#auth-rate-limits).
+**We strongly recommend configuring your own [custom SMTP provider](/docs/guides/auth/auth-smtp)** in your projects to avoid running into issues with sending emails from your project. The built-in email provider is for demonstration purposes only and offers a very low rate limit. You can read more details about the rate limits [here](/docs/guides/deployment/going-into-prod#auth-rate-limits).
If you're testing your Supabase projects, consider configuring an email testing tool like [Mailtrap](https://mailtrap.io/) to test your emails. It's an email sandbox tool that helps debug emails without sending an email to an end user.
diff --git a/apps/docs/content/troubleshooting/pgrst106-the-schema-must-be-one-of-the-following-error-when-querying-an-exposed-schema.mdx b/apps/docs/content/troubleshooting/pgrst106-the-schema-must-be-one-of-the-following-error-when-querying-an-exposed-schema.mdx
index 0ade180ef7e..ceb0f02ba5b 100644
--- a/apps/docs/content/troubleshooting/pgrst106-the-schema-must-be-one-of-the-following-error-when-querying-an-exposed-schema.mdx
+++ b/apps/docs/content/troubleshooting/pgrst106-the-schema-must-be-one-of-the-following-error-when-querying-an-exposed-schema.mdx
@@ -15,7 +15,7 @@ You may encounter a `PGRST106` error, stating `{"code":"PGRST106","message":"The
This error occurs because the `authenticator` role's `pgrst.db_schemas` setting does not include the desired schema. This creates a conflict, as PostgREST relies on this setting to know which schemas it should expose.
**How to Resolve This:**
-To fix this, you need to update the `pgrst.db_schemas` setting for the `authenticator` role. Connect to your database and execute one of the following SQL commands:
+To fix this, you need to update the `pgrst.db_schemas` setting for the `authenticator` role. [Connect to your database](/docs/guides/database/connecting-to-postgres) and execute one of the following SQL commands:
- **To explicitly add your schema:**
If you want to add your specific schema (e.g., `your_schema_name`) alongside existing schemas (like `public`), use the following command. Remember to replace `your_schema_name` with your actual schema name and include all other necessary schemas already defined.
diff --git a/apps/docs/content/troubleshooting/realtime-client-presence-rate-limit-reached.mdx b/apps/docs/content/troubleshooting/realtime-client-presence-rate-limit-reached.mdx
index 2d9337e087a..b8a52dc0345 100644
--- a/apps/docs/content/troubleshooting/realtime-client-presence-rate-limit-reached.mdx
+++ b/apps/docs/content/troubleshooting/realtime-client-presence-rate-limit-reached.mdx
@@ -15,7 +15,7 @@ If a client sends Presence updates too frequently, you may see this error code i
ClientPresenceRateLimitReached
```
-On the client side, the channel receives a `system` error message and is then closed. Any Presence, Broadcast, or Postgres Changes subscriptions on that channel stop until the client reconnects.
+On the client side, the channel receives a `system` error message and is then closed. Any Presence, Broadcast, or [Postgres Changes](/docs/guides/realtime/postgres-changes) subscriptions on that channel stop until the client reconnects.
This error almost always means Presence is being used for high-frequency updates that it isn't designed for. This guide explains the limit, why it exists, and how to fix it.
diff --git a/apps/docs/content/troubleshooting/realtime-messages-not-arriving.mdx b/apps/docs/content/troubleshooting/realtime-messages-not-arriving.mdx
index 31f777f5944..39669125af8 100644
--- a/apps/docs/content/troubleshooting/realtime-messages-not-arriving.mdx
+++ b/apps/docs/content/troubleshooting/realtime-messages-not-arriving.mdx
@@ -22,7 +22,7 @@ channel.subscribe((status, err) => {
1. Check your project isn't paused and Realtime is enabled for it. That toggle ("Enable Realtime service") lives under **Realtime → Settings**. See [Realtime Settings](/docs/guides/realtime/settings).
2. On a private channel, you need an RLS policy that allows the join for your role. Check **Realtime → Policies** on `realtime.messages`. See [Realtime Authorization](/docs/guides/realtime/authorization) for how the policies work. A slow policy can also cause the join to time out instead of failing outright, so check the policy's own performance too, not merely whether it grants access.
-3. Bad JWTs are a common cause. Not expired, has `role` and `exp` claims, and if you're on a third-party auth provider, its JWKS endpoint needs to be reachable. Decode the token (jwt.io, or `atob(token.split('.')[1])`) to check the claims directly. Logging the second argument in `.subscribe((status, err) => ...)` will show you the actual rejection reason instead of leaving you guessing. More detail: [Channel-level system errors](/docs/guides/realtime/protocol#channel-level-system-errors).
+3. Bad JWTs are a common cause. Not expired, has `role` and `exp` claims, and if you're on a [third-party auth provider](/docs/guides/auth/third-party/overview), its JWKS endpoint needs to be reachable. Decode the token (jwt.io, or `atob(token.split('.')[1])`) to check the claims directly. Logging the second argument in `.subscribe((status, err) => ...)` will show you the actual rejection reason instead of leaving you guessing. More detail: [Channel-level system errors](/docs/guides/realtime/protocol#channel-level-system-errors).
4. Reverse proxy or custom SSL termination in front of your app? Make sure it forwards the `Upgrade` and `Connection` headers, or the WebSocket handshake never completes in the first place.
5. Clients need to heartbeat at least every 25 seconds or the connection times out ([Reconnection](/docs/guides/realtime/protocol#reconnection)). So reconnect on unexpected `CLOSED`/`TIMED_OUT` instead of treating either as a hard error: log the status callback so you can tell an expected disconnect apart from a real failure. One caveat: if you're seeing `TIMED_OUT` specifically, that's more often a Node.js version mismatch with your `realtime-js` version than an idle timeout. See [Realtime connections giving `TIMED_OUT` errors](./realtime-connections-timed_out-status).
6. You might be hitting a connection or join-rate limit for your plan (`too_many_connections`, `too_many_joins`). Check the project's usage page in the dashboard, or look for the error code directly in `err`. Plan numbers: [Realtime Limits](/docs/guides/realtime/limits#limits-by-plan). Related: [Realtime: "Concurrent Peak Connections" Quota](./realtime-concurrent-peak-connections-quota-jdDqcp).
diff --git a/apps/docs/content/troubleshooting/realtime-project-suspended-for-exceeding-quotas.mdx b/apps/docs/content/troubleshooting/realtime-project-suspended-for-exceeding-quotas.mdx
index d34aa41b420..8af13dc5e4f 100644
--- a/apps/docs/content/troubleshooting/realtime-project-suspended-for-exceeding-quotas.mdx
+++ b/apps/docs/content/troubleshooting/realtime-project-suspended-for-exceeding-quotas.mdx
@@ -38,7 +38,7 @@ In most cases, quota overages are accidental rather than intentional:
1. **Open a support ticket**: [Contact support](/dashboard/support/new) and include:
- Your project reference ID
- - A description of your Realtime use case (what features use Broadcast, Presence, or Postgres Changes)
+ - A description of your Realtime use case (what features use Broadcast, Presence, or [Postgres Changes](/docs/guides/realtime/postgres-changes))
- An estimate of your expected concurrent connections and message throughput
- Any recent changes to your application that may have caused the spike
diff --git a/apps/docs/content/troubleshooting/realtime-warn-sending-broadcast-message.mdx b/apps/docs/content/troubleshooting/realtime-warn-sending-broadcast-message.mdx
index 59e34a447e0..3e90ef6e909 100644
--- a/apps/docs/content/troubleshooting/realtime-warn-sending-broadcast-message.mdx
+++ b/apps/docs/content/troubleshooting/realtime-warn-sending-broadcast-message.mdx
@@ -80,7 +80,7 @@ Work through these checks before treating the warning as a partition problem:
1. Look for connection errors in your project's Realtime logs, such as failures to validate a JWT signature.
2. Join a channel with the [Realtime Inspector](/dashboard/project/_/realtime/inspector), which connects using your project's own keys. If the Inspector connects and your app does not, your app is sending a different key or a stale user session.
-3. If you rotated your JWT secret or migrated to asymmetric JWT signing keys, sessions issued before the change no longer validate. Existing clients need to sign out and re-authenticate to get a token signed with the current key.
+3. If you rotated your JWT secret or migrated to asymmetric [JWT signing keys](/docs/guides/auth/signing-keys), sessions issued before the change no longer validate. Existing clients need to sign out and re-authenticate to get a token signed with the current key.
Once a client connects, the partitions are created and maintained again.
diff --git a/apps/docs/content/troubleshooting/relation-objects-does-not-exist-error-during-storage-uploads-8f21f0.mdx b/apps/docs/content/troubleshooting/relation-objects-does-not-exist-error-during-storage-uploads-8f21f0.mdx
index 69de7d3fbb2..230f48f7fd2 100644
--- a/apps/docs/content/troubleshooting/relation-objects-does-not-exist-error-during-storage-uploads-8f21f0.mdx
+++ b/apps/docs/content/troubleshooting/relation-objects-does-not-exist-error-during-storage-uploads-8f21f0.mdx
@@ -26,5 +26,5 @@ You can resolve this by updating the role configuration via the [SQL Editor](/da
**Best Practices:**
-- To maintain compatibility with default schema permissions, avoid creating custom Postgres roles for application users.
+- To maintain compatibility with default schema permissions, avoid creating [custom Postgres roles](/docs/guides/database/postgres/roles) for application users.
- Instead, use custom claims within `auth.users.raw_app_meta_data` to manage user-specific logic or permissions.
diff --git a/apps/docs/content/troubleshooting/security-of-anonymous-sign-ins-iOrGCL.mdx b/apps/docs/content/troubleshooting/security-of-anonymous-sign-ins-iOrGCL.mdx
index bb9ab7e9cbd..7467e833bcc 100644
--- a/apps/docs/content/troubleshooting/security-of-anonymous-sign-ins-iOrGCL.mdx
+++ b/apps/docs/content/troubleshooting/security-of-anonymous-sign-ins-iOrGCL.mdx
@@ -11,7 +11,7 @@ We want to clarify and provide reassurance on this topic.
## Security overview:
-Enabling anonymous sign-ins on your project does not reduce its security. Here's why:
+Enabling [anonymous sign-ins](/docs/guides/auth/auth-anonymous) on your project does not reduce its security. Here's why:
- Same as Regular Users: Anonymous users function like regular users within your project. They have unique user IDs and their own records in the authentication tables.
- Security Policies: All role-based security policies (RLS) applicable to regular users also apply to anonymous users.
diff --git a/apps/docs/content/troubleshooting/supavisor-and-connection-terminology-explained-9pr_ZO.mdx b/apps/docs/content/troubleshooting/supavisor-and-connection-terminology-explained-9pr_ZO.mdx
index ad0f4472c28..6a66cb33a38 100644
--- a/apps/docs/content/troubleshooting/supavisor-and-connection-terminology-explained-9pr_ZO.mdx
+++ b/apps/docs/content/troubleshooting/supavisor-and-connection-terminology-explained-9pr_ZO.mdx
@@ -54,7 +54,7 @@ postgres://postgres.obfwhevidiamwdwki:[YPASSWORD]@aws-0-ca-central-1.pooler.supa
Postgres connections use the Postgres Wire Protocol (PWP) rather than HTTP. PWP acts like a WebSocket: once a connection is made, it stays open and active until the client disconnects.
-If too many connections are held by idle or greedy clients, other application servers won’t be able to connect to your database. Transaction mode helps avoid this problem by allowing clients to access the database connections only when they are running a query. This reduces the chances of hitting the maximum direct connection limit.
+If too many connections are held by idle or greedy clients, other application servers won’t be able to [connect to your database](/docs/guides/database/connecting-to-postgres). Transaction mode helps avoid this problem by allowing clients to access the database connections only when they are running a query. This reduces the chances of hitting the maximum direct connection limit.
## Session mode: