Miranda Limonczenko 0cb07c30f7 docs: fix the local development anchor and the propagation claim ...

Two claims on the custom claims and RBAC guide that leave a reader with
a wrong outcome.

The "local development" link pointed at
/docs/guides/auth/auth-hooks#local-development, and no heading by that
name exists. The section is "Developing", so the one link that carries
the local `config.toml` setting dropped the reader at the top of the
page. Renaming the heading restores the anchor rather than repointing
the link, because the Slack Clone example's own `config.toml` comment
expects the same anchor in two places. Nothing links to `#developing`.

The conclusion said the setup "automatically propagates to Supabase
Auth", which reads as though a role change reaches open sessions. It
reaches the next token the hook issues. Say when a change lands and how
to make it land now.

2026-09-24 17:44:45 -07:00

..

_partials

updated guidance for logs pricing, revised manage logs usage pages, introduction of the grace period(#49656)

2026-09-24 10:27:23 -07:00

guides

docs: fix the local development anchor and the propagation claim

2026-09-24 17:44:45 -07:00

troubleshooting

feat(studio): rename Replication to Pipelines (#50637)

2026-09-23 08:52:07 +10:00

navigation.references.ts

docs(csharp): add new C# Reference for v8.0.0 (#50116)

2026-09-14 10:07:26 +02:00