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 2) (#51857)

Kody Jackson3de2439b9f6b
diff --git a/apps/docs/content/guides/getting-started/tutorials/with-sveltekit.mdx b/apps/docs/content/guides/getting-started/tutorials/with-sveltekit.mdx
index b9d3c1d6b20..9973574aa00 100644
--- a/apps/docs/content/guides/getting-started/tutorials/with-sveltekit.mdx
+++ b/apps/docs/content/guides/getting-started/tutorials/with-sveltekit.mdx
@@ -177,7 +177,7 @@ You can also customize emails sent out to new users, including the email's looks
#### Confirmation endpoint
-As this is a server-side rendering (SSR) environment, you need to create a server endpoint responsible for exchanging the `token_hash` for a session.
+As this is a [server-side rendering](/docs/guides/auth/server-side) (SSR) environment, you need to create a server endpoint responsible for exchanging the `token_hash` for a session.
The following code snippet performs the following steps:
diff --git a/apps/docs/content/guides/local-development.mdx b/apps/docs/content/guides/local-development.mdx
index ded657c6113..f0727a45de0 100644
--- a/apps/docs/content/guides/local-development.mdx
+++ b/apps/docs/content/guides/local-development.mdx
@@ -155,7 +155,7 @@ With the default ports, `supabase start` runs one local project per machine. To
The Supabase CLI is a tool that enables developers to run Supabase services locally and manage hosted projects directly from the terminal. It provides a suite of commands for various tasks, including:
- Setting up and managing local development environments
-- Generating TypeScript types for your database schema
+- [Generating TypeScript types](/docs/guides/api/rest/generating-types) for your database schema
- Handling [database migrations](/docs/guides/local-development/database-migrations) and [declarative database schemas](/docs/guides/local-development/declarative-database-schemas)
- Managing environment variables and secrets
- Deploying your project to the Supabase platform
diff --git a/apps/docs/content/guides/local-development/declarative-database-schemas.mdx b/apps/docs/content/guides/local-development/declarative-database-schemas.mdx
index e82961d30b7..598fdaaa519 100644
--- a/apps/docs/content/guides/local-development/declarative-database-schemas.mdx
+++ b/apps/docs/content/guides/local-development/declarative-database-schemas.mdx
@@ -348,7 +348,7 @@ With `pg_cron` enabled, declare each job in a SQL file under `supabase/schemas/`
Two checks gate `sync` on a schema tree the CLI didn't generate:
-- If your migrations call `pg_net` (for example, database webhooks), add `[experimental.webhooks]` with `enabled = true` to `config.toml` first. The section isn't part of the default `init` template.
+- If your migrations call `pg_net` (for example, [database webhooks](/docs/guides/database/webhooks)), add `[experimental.webhooks]` with `enabled = true` to `config.toml` first. The section isn't part of the default `init` template.
- Declare the extensions your schema files depend on. The check trips for `pg_net` and for extensions your own migrations create. When it does, interactive `sync` offers to add the missing declaration and re-plan, or to stage a fresh export into a sibling `-next` directory and print the commands to adopt it. A non-interactive run only prints those commands. Extensions the local stack already ships, such as `pgcrypto` and `uuid-ossp`, don't trip the check even when undeclared, so declare them yourself.
## Declarative schemas on the legacy `migra` engine [#declarative-schemas-on-the-legacy-migra-engine]
diff --git a/apps/docs/content/guides/observability.mdx b/apps/docs/content/guides/observability.mdx
index 5ddf6197d23..e03e6f1f7c4 100644
--- a/apps/docs/content/guides/observability.mdx
+++ b/apps/docs/content/guides/observability.mdx
@@ -7,7 +7,7 @@ Use project data to understand what is happening, investigate issues, and give a
## Read project data [#metrics-api]
-Query logs for events, inspect database statistics, or review advisor findings. Use Reports to visualize signals and the Metrics API to export them.
+Query logs for events, inspect database statistics, or review advisor findings. Use Reports to visualize signals and the [Metrics API](/docs/guides/observability/metrics) to export them.
<ContentListings id="telemetry-access-what" />
diff --git a/apps/docs/content/guides/observability/metrics/grafana-cloud.mdx b/apps/docs/content/guides/observability/metrics/grafana-cloud.mdx
index 42f894f2b87..e4a7ff4a304 100644
--- a/apps/docs/content/guides/observability/metrics/grafana-cloud.mdx
+++ b/apps/docs/content/guides/observability/metrics/grafana-cloud.mdx
@@ -4,7 +4,7 @@ title: 'Metrics API with Grafana Cloud'
description: 'Use Grafana Cloud’s managed Prometheus to visualize Supabase metrics'
---
-Grafana Cloud gives you a fully managed Prometheus endpoint plus hosted Grafana dashboards, which makes it the fastest way to explore the Supabase Metrics API without operating your own infrastructure.
+Grafana Cloud gives you a fully managed Prometheus endpoint plus hosted Grafana dashboards, which makes it the fastest way to explore the Supabase [Metrics API](/docs/guides/observability/metrics) without operating your own infrastructure.
## Installation
diff --git a/apps/docs/content/guides/observability/metrics/grafana-self-hosted.mdx b/apps/docs/content/guides/observability/metrics/grafana-self-hosted.mdx
index aa0de4b6ee5..8fb270a322a 100644
--- a/apps/docs/content/guides/observability/metrics/grafana-self-hosted.mdx
+++ b/apps/docs/content/guides/observability/metrics/grafana-self-hosted.mdx
@@ -4,7 +4,7 @@ title: 'Metrics API with Prometheus & Grafana (self-hosted)'
description: 'Deploy Prometheus and Grafana yourself to monitor Supabase metrics'
---
-Self-hosting [Prometheus](https://prometheus.io/docs/prometheus/latest/installation/) and Grafana gives you full control over retention, alert routing, and dashboards. The Supabase Metrics API slots into any standard Prometheus scrape job, so you can run everything locally, on a VM, or inside Kubernetes.
+Self-hosting [Prometheus](https://prometheus.io/docs/prometheus/latest/installation/) and Grafana gives you full control over retention, alert routing, and dashboards. The Supabase [Metrics API](/docs/guides/observability/metrics) slots into any standard Prometheus scrape job, so you can run everything locally, on a VM, or inside Kubernetes.
<Admonition type="caution">
diff --git a/apps/docs/content/guides/observability/metrics/vendor-agnostic.mdx b/apps/docs/content/guides/observability/metrics/vendor-agnostic.mdx
index 12cb2746b9d..03d49a52238 100644
--- a/apps/docs/content/guides/observability/metrics/vendor-agnostic.mdx
+++ b/apps/docs/content/guides/observability/metrics/vendor-agnostic.mdx
@@ -62,7 +62,7 @@ No matter which collector you use, you need to hit the Metrics API once per minu
- Start with the [example alert rules](https://github.com/supabase/supabase-grafana/blob/main/docs/example-alerts.md) and adapt thresholds for your workload sizes.
- Pipe alerts into PagerDuty, Slack, Opsgenie, or any other compatible target.
-- Combine Metrics API data with log drains, Query Performance, and Advisors to build right-sizing playbooks.
+- Combine Metrics API data with [log drains](/docs/guides/observability/log-drains), Query Performance, and Advisors to build right-sizing playbooks.
## 5. Multi-project setups
diff --git a/apps/docs/content/guides/platform/clone-project.mdx b/apps/docs/content/guides/platform/clone-project.mdx
index 3b4e5f1ee20..dba5e2e17c9 100644
--- a/apps/docs/content/guides/platform/clone-project.mdx
+++ b/apps/docs/content/guides/platform/clone-project.mdx
@@ -24,7 +24,7 @@ You can clone your Supabase project by restoring your data from an existing proj
- Auth settings & API keys
- Realtime settings
- Database extensions and settings
-- Read replicas
+- [Read replicas](/docs/guides/platform/read-replicas)
Whether you're using physical backups or Point-in-Time recovery (PITR), this feature allows you to duplicate project data with ease, perform testing safely, or recover data for analysis. Access to this feature is exclusive to users on paid plans and requires that physical backups are enabled for the source project.
diff --git a/apps/docs/content/guides/platform/manage-your-usage/disk-iops.mdx b/apps/docs/content/guides/platform/manage-your-usage/disk-iops.mdx
index 9ad57aa1bd4..0634667984a 100644
--- a/apps/docs/content/guides/platform/manage-your-usage/disk-iops.mdx
+++ b/apps/docs/content/guides/platform/manage-your-usage/disk-iops.mdx
@@ -17,7 +17,7 @@ Disk IOPS Hours are **not** covered by the [Spend Cap](/docs/guides/platform/cos
<Admonition type="note">
-Launching a Read Replica creates an additional database with its own dedicated disk. Read Replicas inherit the primary database's disk IOPS settings. You are charged for the provisioned IOPS of the Read Replica. Refer to [Manage Read Replica usage](/docs/guides/platform/manage-your-usage/read-replicas) for details on billing.
+Launching a [Read Replica](/docs/guides/platform/read-replicas) creates an additional database with its own dedicated disk. Read Replicas inherit the primary database's disk IOPS settings. You are charged for the provisioned IOPS of the Read Replica. Refer to [Manage Read Replica usage](/docs/guides/platform/manage-your-usage/read-replicas) for details on billing.
</Admonition>
diff --git a/apps/docs/content/guides/platform/manage-your-usage/disk-throughput.mdx b/apps/docs/content/guides/platform/manage-your-usage/disk-throughput.mdx
index 0b75a4693f4..efd9fb7eeec 100644
--- a/apps/docs/content/guides/platform/manage-your-usage/disk-throughput.mdx
+++ b/apps/docs/content/guides/platform/manage-your-usage/disk-throughput.mdx
@@ -17,7 +17,7 @@ Disk Throughput is **not** covered by the [Spend Cap](/docs/guides/platform/cost
<Admonition type="note">
-Launching a Read Replica creates an additional database with its own dedicated disk. Read Replicas inherit the primary database's disk throughput settings. You are charged for the provisioned throughput of the Read Replica.
+Launching a [Read Replica](/docs/guides/platform/read-replicas) creates an additional database with its own dedicated disk. Read Replicas inherit the primary database's disk throughput settings. You are charged for the provisioned throughput of the Read Replica.
</Admonition>
diff --git a/apps/docs/content/guides/platform/manage-your-usage/egress.mdx b/apps/docs/content/guides/platform/manage-your-usage/egress.mdx
index fcab09947c1..fb08b45a592 100644
--- a/apps/docs/content/guides/platform/manage-your-usage/egress.mdx
+++ b/apps/docs/content/guides/platform/manage-your-usage/egress.mdx
@@ -5,7 +5,7 @@ title: 'Manage Egress usage'
## What you are charged for
-You are charged for the network data transmitted out of the system to a connected client. Egress is incurred by all services - Database, Auth, Storage, Edge Functions, Realtime and Log Drains.
+You are charged for the network data transmitted out of the system to a connected client. Egress is incurred by all services - Database, Auth, Storage, Edge Functions, Realtime and [Log Drains](/docs/guides/observability/log-drains).
### Database Egress
diff --git a/apps/docs/content/guides/platform/manage-your-usage/ipv4.mdx b/apps/docs/content/guides/platform/manage-your-usage/ipv4.mdx
index 8c004f63755..2236f8f56f9 100644
--- a/apps/docs/content/guides/platform/manage-your-usage/ipv4.mdx
+++ b/apps/docs/content/guides/platform/manage-your-usage/ipv4.mdx
@@ -15,7 +15,7 @@ IPv4 Hours are **not** covered by the [Spend Cap](/docs/guides/platform/cost-con
<Admonition type="note">
-If the primary database has a dedicated IPv4 address configured, its Read Replicas are also assigned one, with charges for each.
+If the primary database has a dedicated IPv4 address configured, its [Read Replicas](/docs/guides/platform/read-replicas) are also assigned one, with charges for each.
</Admonition>
diff --git a/apps/docs/content/guides/platform/manage-your-usage/monthly-active-users-third-party.mdx b/apps/docs/content/guides/platform/manage-your-usage/monthly-active-users-third-party.mdx
index d7746c5fff1..ce93605fd99 100644
--- a/apps/docs/content/guides/platform/manage-your-usage/monthly-active-users-third-party.mdx
+++ b/apps/docs/content/guides/platform/manage-your-usage/monthly-active-users-third-party.mdx
@@ -5,7 +5,7 @@ title: 'Manage Monthly Active Third-Party Users usage'
## What you are charged for
-You are charged for the number of distinct users who sign in or refresh their token during the billing cycle using a third-party authentication provider (Clerk, Firebase Auth, Auth0, AWS Cognito). Each unique user is counted only once per billing cycle, regardless of how many times they authenticate. These users are referred to as "Third-Party MAUs".
+You are charged for the number of distinct users who sign in or refresh their token during the billing cycle using a third-party authentication provider ([Clerk](/docs/guides/auth/third-party/clerk), [Firebase Auth](/docs/guides/auth/third-party/firebase-auth), [Auth0](/docs/guides/auth/third-party/auth0), [AWS Cognito](/docs/guides/auth/third-party/aws-cognito)). Each unique user is counted only once per billing cycle, regardless of how many times they authenticate. These users are referred to as "Third-Party MAUs".
### Example
diff --git a/apps/docs/content/guides/platform/manage-your-usage/monthly-active-users.mdx b/apps/docs/content/guides/platform/manage-your-usage/monthly-active-users.mdx
index 2aea88c03ca..6903e08530a 100644
--- a/apps/docs/content/guides/platform/manage-your-usage/monthly-active-users.mdx
+++ b/apps/docs/content/guides/platform/manage-your-usage/monthly-active-users.mdx
@@ -5,7 +5,7 @@ title: 'Manage Monthly Active Users usage'
## What you are charged for
-You are charged for the number of distinct users who sign in or refresh their token during the billing cycle (including social login with e.g. Google, Facebook, GitHub). Each unique user is counted only once per billing cycle, regardless of how many times they authenticate. These users are referred to as "MAUs".
+You are charged for the number of distinct users who sign in or refresh their token during the billing cycle (including [social login](/docs/guides/auth/social-login) with e.g. Google, Facebook, GitHub). Each unique user is counted only once per billing cycle, regardless of how many times they authenticate. These users are referred to as "MAUs".
### Example
diff --git a/apps/docs/content/guides/platform/multi-factor-authentication.mdx b/apps/docs/content/guides/platform/multi-factor-authentication.mdx
index fd9a099c51e..bc9f53a020e 100644
--- a/apps/docs/content/guides/platform/multi-factor-authentication.mdx
+++ b/apps/docs/content/guides/platform/multi-factor-authentication.mdx
@@ -18,7 +18,7 @@ Currently, Supabase supports adding a unique time-based one-time password (TOTP)
## Enable MFA
-You can enable MFA for your user account under your [Supabase account settings](/dashboard/account/security). Enabling MFA will result in all other user sessions to be automatically logged out and forced to sign in again with MFA.
+You can enable MFA for your user account under your [Supabase account settings](/dashboard/account/security). Enabling MFA will result in all other [user sessions](/docs/guides/auth/sessions) to be automatically logged out and forced to sign in again with MFA.
<Admonition type="note">
diff --git a/apps/docs/content/guides/platform/postgres-connection-logging.mdx b/apps/docs/content/guides/platform/postgres-connection-logging.mdx
index b0ef15ab47d..e823658b455 100644
--- a/apps/docs/content/guides/platform/postgres-connection-logging.mdx
+++ b/apps/docs/content/guides/platform/postgres-connection-logging.mdx
@@ -13,7 +13,7 @@ By default, Supabase sets `log_connections` to off for new projects and you must
Existing projects may retain different settings depending on plan and compliance configuration:
- **Team, Enterprise, and HIPAA organizations** — Connection logging is typically enabled to support audit requirements.
-- **HIPAA projects** — Supabase enables connection logging when a project is marked as high compliance. The [Security Advisor](/dashboard/project/_/advisors/security) warns if connection logging is later disabled.
+- **[HIPAA projects](/docs/guides/platform/hipaa-projects)** — Supabase enables connection logging when a project is marked as high compliance. The [Security Advisor](/dashboard/project/_/advisors/security) warns if connection logging is later disabled.
## Compliance considerations
diff --git a/apps/docs/content/guides/platform/regions.mdx b/apps/docs/content/guides/platform/regions.mdx
index 8662452218d..3fff69a270d 100644
--- a/apps/docs/content/guides/platform/regions.mdx
+++ b/apps/docs/content/guides/platform/regions.mdx
@@ -16,7 +16,7 @@ For most projects, we recommend choosing a general region. Supabase will deploy
<SmartRegionsList />
-Note: General regions aren’t yet supported for read replicas or management via the API.
+Note: General regions aren’t yet supported for [read replicas](/docs/guides/platform/read-replicas) or management via the API.
## Specific regions
diff --git a/apps/docs/content/guides/platform/temporary-access.mdx b/apps/docs/content/guides/platform/temporary-access.mdx
index 0c9eec50002..5551c7055ed 100644
--- a/apps/docs/content/guides/platform/temporary-access.mdx
+++ b/apps/docs/content/guides/platform/temporary-access.mdx
@@ -55,7 +55,7 @@ curl -X PUT "https://api.supabase.com/v1/projects/$PROJECT_REF/jit-access" \
## Configure user access
-Once temporary access has been enabled, project users must be authorized and mapped to Postgres roles they are allowed to access. Each user can be authorized to "assume" one or more Postgres roles using temporary access.
+Once temporary access has been enabled, project users must be authorized and mapped to [Postgres roles](/docs/guides/database/postgres/roles) they are allowed to access. Each user can be authorized to "assume" one or more Postgres roles using temporary access.
When a user is authorized to assume a Postgres role, the user's Personal Access Token (PAT) will be used as the password for the Postgres role.
diff --git a/apps/docs/content/guides/queues.mdx b/apps/docs/content/guides/queues.mdx
index cec78bc6f46..2dbfc6032d2 100644
--- a/apps/docs/content/guides/queues.mdx
+++ b/apps/docs/content/guides/queues.mdx
@@ -6,7 +6,7 @@ tocVideo: UEwfaElBnZk
Supabase Queues is a Postgres-native durable Message Queue system with guaranteed delivery built on the [pgmq database extension](https://github.com/tembo-io/pgmq). It offers developers a seamless way to persist and process Messages in the background while improving the resiliency and scalability of their applications and services.
-Queues couples the reliability of Postgres with the simplicity Supabase's platform and developer experience, enabling developers to manage Background Tasks with zero configuration.
+Queues couples the reliability of Postgres with the simplicity Supabase's platform and developer experience, enabling developers to manage [Background Tasks](/docs/guides/functions/background-tasks) with zero configuration.
## Features
diff --git a/apps/docs/content/guides/realtime/benchmarks.mdx b/apps/docs/content/guides/realtime/benchmarks.mdx
index 170609d4848..85c6f6e6e6b 100644
--- a/apps/docs/content/guides/realtime/benchmarks.mdx
+++ b/apps/docs/content/guides/realtime/benchmarks.mdx
@@ -4,7 +4,7 @@ subtitle: 'Scalability Benchmarks for Supabase Realtime.'
description: 'Scalability Benchmarks for Supabase Realtime.'
---
-This guide explores the scalability of Realtime's features: Broadcast, Presence, and Postgres Changes.
+This guide explores the scalability of Realtime's features: Broadcast, Presence, and [Postgres Changes](/docs/guides/realtime/postgres-changes).
## Methodology
diff --git a/apps/docs/content/guides/realtime/concepts.mdx b/apps/docs/content/guides/realtime/concepts.mdx
index 072fe519a68..8df56b6946c 100644
--- a/apps/docs/content/guides/realtime/concepts.mdx
+++ b/apps/docs/content/guides/realtime/concepts.mdx
@@ -40,7 +40,7 @@ The connections include:
- **Migrations**: Two temporary connections to run database migrations when needed
- **Authorization**: Configurable connection pool to check authorization policies on join that are always started.
- **Broadcast from database**: One connection to receive data from replication slot used to broadcast the changes to the clients that is always started.
-- **Postgres Changes**: Multiple connection pools required. These pools are only started if you use Postgres Changes.
+- **[Postgres Changes](/docs/guides/realtime/postgres-changes)**: Multiple connection pools required. These pools are only started if you use Postgres Changes.
- **Subscription management**: To manage the subscribers to Postgres Changes
- **Subscription cleanup**: To cleanup the subscribers to Postgres Changes
- **WAL pull**: To pull the changes from the database
diff --git a/apps/docs/content/guides/realtime/realtime-listening-flutter.mdx b/apps/docs/content/guides/realtime/realtime-listening-flutter.mdx
index 0123d5f47a4..e41978396c9 100644
--- a/apps/docs/content/guides/realtime/realtime-listening-flutter.mdx
+++ b/apps/docs/content/guides/realtime/realtime-listening-flutter.mdx
@@ -5,6 +5,6 @@ description: 'Listening to real-time changes on the database with Flutter'
sidebar_label: 'Videos'
---
-The Postgres Changes extension listens for database changes and sends them to clients which enables you to receive database changes in real-time.
+The [Postgres Changes](/docs/guides/realtime/postgres-changes) extension listens for database changes and sends them to clients which enables you to receive database changes in real-time.
<YouTube id="gboTC2lcgzw" title="Listening to Postgres changes with Flutter" />
diff --git a/apps/docs/content/guides/realtime/realtime-with-nextjs.mdx b/apps/docs/content/guides/realtime/realtime-with-nextjs.mdx
index 954cfc70093..136686af3bf 100644
--- a/apps/docs/content/guides/realtime/realtime-with-nextjs.mdx
+++ b/apps/docs/content/guides/realtime/realtime-with-nextjs.mdx
@@ -5,7 +5,7 @@ description: 'Client & Server Components in Next.js with Realtime Updates'
sidebar_label: 'Videos'
---
-In this guide, we explore the best ways to receive real-time Postgres changes with your Next.js application.
+In this guide, we explore the best ways to receive real-time [Postgres changes](/docs/guides/realtime/postgres-changes) with your Next.js application.
We'll show both client and server side updates, and explore which option is best.
<YouTube id="YR-xP6PPXXA" title="Building a Realtime app with Next.js" />
diff --git a/apps/docs/content/guides/resources/glossary.mdx b/apps/docs/content/guides/resources/glossary.mdx
index d908290152a..94ebd9c72bc 100644
--- a/apps/docs/content/guides/resources/glossary.mdx
+++ b/apps/docs/content/guides/resources/glossary.mdx
@@ -28,7 +28,7 @@ Authorization (often abbreviated `authz.`) is the process of verifying if a cert
## Identity provider
-An identity provider is software or service that allows third-party applications to identify users without the exchange of passwords. Social login and enterprise single-sign on won't be possible without identity providers.
+An identity provider is software or service that allows third-party applications to identify users without the exchange of passwords. [Social login](/docs/guides/auth/social-login) and enterprise single-sign on won't be possible without identity providers.
Social login platforms typically use the OAuth protocol, while enterprise single-sign on is based on the OIDC or SAML protocols.
diff --git a/apps/docs/content/guides/self-hosting.mdx b/apps/docs/content/guides/self-hosting.mdx
index fb76d8f31d6..3eb1862f8da 100644
--- a/apps/docs/content/guides/self-hosting.mdx
+++ b/apps/docs/content/guides/self-hosting.mdx
@@ -15,7 +15,7 @@ Self-hosting is a good fit if you need full control over your data, have complia
Self-hosted Supabase runs as a single project, which means that Studio doesn't support multiple organizations or projects. Most settings are configured through [environment variables](https://github.com/supabase/supabase/blob/master/docker/.env.example).
-Some features of the managed platform aren't available when self-hosting: branching, advanced metrics beyond logs, managed backups and PITR, analytics and vector buckets, ETL, and the Management API. To collect logs and metrics yourself, see the community-maintained [observability project](https://github.com/supabase-community/supabase-observability).
+Some features of the managed platform aren't available when self-hosting: branching, advanced metrics beyond logs, managed backups and PITR, analytics and [vector buckets](/docs/guides/storage/vector/introduction), ETL, and the Management API. To collect logs and metrics yourself, see the community-maintained [observability project](https://github.com/supabase-community/supabase-observability).
### Not the same as local development
diff --git a/apps/docs/content/guides/self-hosting/self-hosted-auth-keys.mdx b/apps/docs/content/guides/self-hosting/self-hosted-auth-keys.mdx
index 868864ce4e6..887c0002a0e 100644
--- a/apps/docs/content/guides/self-hosting/self-hosted-auth-keys.mdx
+++ b/apps/docs/content/guides/self-hosting/self-hosted-auth-keys.mdx
@@ -163,7 +163,7 @@ sh run.sh recreate
<Admonition type="note">
-Rotating new API keys does not invalidate existing user sessions. User session JWTs issued by Auth are unaffected because they are verified using the asymmetric key pair, which remains unchanged.
+Rotating new API keys does not invalidate existing [user sessions](/docs/guides/auth/sessions). User session JWTs issued by Auth are unaffected because they are verified using the asymmetric key pair, which remains unchanged.
</Admonition>
diff --git a/apps/docs/content/guides/self-hosting/self-hosted-functions.mdx b/apps/docs/content/guides/self-hosting/self-hosted-functions.mdx
index 432ade2b385..fccf8c1c699 100644
--- a/apps/docs/content/guides/self-hosting/self-hosted-functions.mdx
+++ b/apps/docs/content/guides/self-hosting/self-hosted-functions.mdx
@@ -199,7 +199,7 @@ ssh user@<your-domain> 'cd /path/to/self-hosted && sh run.sh restart functions'
If you have existing functions on Supabase platform, you can download them and run them on your self-hosted instance. There are two ways to get the function source code:
- **Dashboard** - open the function details in Dashboard and click **Download**.
-- **Local development & CLI** - run `supabase functions download <function-name> --project-ref <ref>` to download the source.
+- **[Local development & CLI](/docs/guides/local-development)** - run `supabase functions download <function-name> --project-ref <ref>` to download the source.
Use `scp` to copy the function into `volumes/functions/<function-name>/` on your self-hosted instance, then restart the functions service.