Add public api token workspace permission detail #5088
Merged
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
**Before this PR:** Segment Documentation does not state the required role / user permissions required to create a Public API Token **After this PR:** Segment Documentation now explicitly states the required role / user permissions required to create a Public API Token **Reason that prompted this change:** JPMC Question / [Finding Answer in Slack](https://twilio.slack.com/archives/C018FB6PZ0C/p1656694188032489?thread_ts=1656692127.704029&cid=C018FB6PZ0C)
rchinn1
added
the
content-update
rchinn1
approved these changes
Jul 28, 2023
rchinn1
changed the title
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
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.
Proposed changes
Before this PR:
Segment Documentation does not state the required role / user permissions required to create a Public API Token
After this PR:
Segment Documentation now explicitly states the required role / user permissions required to create a Public API Token
Reason that prompted this change:
JPMC Question / Finding Answer in Slack
Merge timing