Separate OAuth2 Scopes table

[advaith1]

This PR addresses some issues with the OAuth2 Scopes table by separating it into multiple groups:

• Public User Scopes (normal)
• Guild Scopes (commands/bot)
• Other Scopes (webhooks/client creds)
• Restricted Scopes (devs/testers only, unless approved)
• Private Scopes (approval required)

I think this is a better alternative to the controversial #5127, as it should resolve confusion without removing documentation. I believe the documentation should continue to list all scopes, as it can be useful.

View updated section

[AlmostSuspense]

perhaps there should be a section about what "approval" is, to avoid more confusion from users since i believe there's no formal approval process?

[Mehgugs]

What does "applications.store.update" actually authorize, I cannot find an endpoint that the token can use: are you sure that is not behind approval?

[advaith1]

perhaps there should be a section about what "approval" is, to avoid more confusion from users since i believe there's no formal approval process?

tried to clarify this with

Some scopes require approval from Discord to use, and there is no public application process.

could add more information tho

---

What does "applications.store.update" actually authorize, I cannot find an endpoint that the token can use: are you sure that is not behind approval?

yeah this scope does not require approval; this allows reading and managing store & achievement data for the user's apps with dev licenses, achievement endpoints are documented at https://discord.com/developers/docs/game-sdk/achievements#the-api-way

maybe I should add a link to that in the scopes table