Changelog: Clarification on Permission Splits for Expressions and Events #6578
Conversation
This file contains 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
3 tasks
shaydewael
pushed a commit
to Jupith/discord-api-docs
that referenced
this pull request
May 14, 2024
…nts (discord#6578) * Rollback previous perm split changelog * Add dev note to CREATE_GUILD_EXPRESSIONS and CREATE_EVENTS
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.
The existing behavior for
MANAGE_GUILD_EXPRESSIONSandMANAGE_EVENTSwill not be changing. These permissions will continue to allow your bot users to create, update and delete expressions/events. No action will be needed if you plan to continue using these permissions.CREATE_GUILD_EXPRESSIONSandCREATE_EVENTSas documented today are permissions available to users and roles but are not yet available for apps. We will share a follow up changelog once they are available.