Repository navigation
docs: list Plain API key permissions for support ticketing - #8403
Merged
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
cdxker
approved these changes
Nov 11, 2026
This branch was successfully deployed
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
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.
Lists the five permissions a Plain API key needs for direct support ticketing, so admins can create the key correctly before connecting.
Based on the merged assistant change that adds direct support ticketing to Plain and Zendesk.
Note
Low Risk
Documentation-only updates with no runtime or configuration behavior changes.
Overview
Adds a prerequisite checklist for Plain direct support ticketing: admins must create an API key with
customer:create,customer:edit,customer:read,thread:create, andthread:readbefore clicking Connect.The Scopes misconfigured troubleshooting note now refers to any of the required permissions instead of a generic “permission ticketing needs.”
Reviewed by Cursor Bugbot for commit 160a60f. Bugbot is set up for automated code reviews on this repo. Configure here.