Social SDK: Add OAuth Communications Scope warnings #7653
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| * [Presence & Rich Presence](/docs/discord-social-sdk/core-concepts#presence-rich-presence) | ||
|
|
||
| The Social SDK provides the helper method [`Client::GetDefaultPresenceScopes`], which returns `openid sdk.social_layer_presence`, | ||
| that you can use when setting up your OAuth2 flow, for integrations that only needs the above functionality. |
There was a problem hiding this comment.
Suggested change
| that you can use when setting up your OAuth2 flow, for integrations that only needs the above functionality. | |
| that you can use when setting up your OAuth2 flow, for integrations that only need the above functionality. |
Not sure which is grammatically correct but I think this reads better
Devs keep running into the issue that they aren't aware that to use communication features, they need to enable communication OAuth scopes (mainly because we're not explicit about it anywhere). This aims to fix this! This PR includes: - Reorganize core concepts page to prioritize OAuth scopes - Add implementation details to OAuth guide - Add warnings to guides using Communications features about scope requirements
markmandel
force-pushed
the
social-sdk/scopes
branch
from
5378035 to
e1e1637
Compare
anthonydiscord
approved these changes
Jun 30, 2025
|
|
||
| ### Default Communication Scopes | ||
|
|
||
| The communications features are currently available but have limited access. Those features **require** the following scope |
There was a problem hiding this comment.
Suggested change
| The communications features are currently available but have limited access. Those features **require** the following scope | |
| The communications features are currently available but have limited access. Those features **require** the scope |
I think this reads a little better
|
Preview: |
|
|
markmandel
force-pushed
the
social-sdk/scopes
branch
from
bf901ec to
23190e5
Compare
mazylol
pushed a commit
to mazylol/discord-api-docs
that referenced
this pull request
Jul 3, 2025
* Social SDK: Add OAuth Communications Scope warnings Devs keep running into the issue that they aren't aware that to use communication features, they need to enable communication OAuth scopes (mainly because we're not explicit about it anywhere). This aims to fix this! This PR includes: - Reorganize core concepts page to prioritize OAuth scopes - Add implementation details to OAuth guide - Add warnings to guides using Communications features about scope requirements * Review updates.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Devs keep running into the issue that they aren't aware that to use communication features, they need to enable communication OAuth scopes (mainly because we're not explicit about it anywhere).
This aims to fix this! This PR includes: