Miranda Limonczenko
0cb07c30f7
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.
Reference Docs
Supabase Reference Docs
Maintainers
If you are a maintainer of any tools in the Supabase ecosystem, you can use this site to provide documentation for the tools & libraries that you maintain.
DocSpec
We use documentation specifications which can be used to generate human-readable docs.
- OpenAPI: for documenting API endpoints.
- SDKSpec (custom to Supabase): for SDKs and client libraries.
- ConfigSpec (custom to Supabase): for configuration options.
- CLISpec (custom to Supabase): for CLI commands and usage.
The benefit of using custom specifications is that we can generate many other types from a strict schema (eg, HTML and manpages). It also means that we can switch to any documentation system we want. On this site we use Next.js, but on Supabase's official website, we use a custom React site and expose only a subset of the available API for each tool.
Contributing
To contribute to docs, see the developers' guide and contributing guide. If you write with an AI coding agent, use the /write-the-docs skill to draft and /edit-the-docs to revise an existing page.