From c4edde20ffa3d0afc21f2849175dc90c04a106c9 Mon Sep 17 00:00:00 2001 From: Abdelrahman Essawy Date: Tue, 1 Sep 2026 08:04:47 +0300 Subject: [PATCH] docs(scopes): drop the pre-scopes migration section Every sentence in it is now false. Keys with no recorded permissions no longer hold everything a key may hold, they hold nothing, and there are none left on production anyway. Apps that connected with media:full had those grants revoked when the alias was retired, and the alias now expands to no scopes at all. A migration note outlives its migration by describing a state nobody is in, which is worse than saying nothing. --- concepts/scopes.mdx | 8 -------- 1 file changed, 8 deletions(-) diff --git a/concepts/scopes.mdx b/concepts/scopes.mdx index f69b7ac..9e5bb2d 100644 --- a/concepts/scopes.mdx +++ b/concepts/scopes.mdx @@ -123,14 +123,6 @@ It is a `403`, not a `401`: the credential authenticated correctly and presentin help. Read the `scope` parameter to see what to ask for, then create a key that carries it or reconnect the app and allow that area. -## Keys and apps that predate scopes - -Keys created before scopes hold everything a key may hold and keep working unchanged. - -Apps connected before scopes asked for `media:full`, which covers jobs, assets and reading billing. -That does not include key management, so those connections cannot create or revoke API keys. -Reconnecting the app grants it the current set. - ## See also - [MCP server](/mcp-server): connecting an app over OAuth