DOCS-1767 - Update Search Job API required capabilities and Manage Access Keys - #6934
Open
JV0812 wants to merge 6 commits into
Open
DOCS-1767 - Update Search Job API required capabilities and Manage Access Keys#6934JV0812 wants to merge 6 commits into
JV0812 wants to merge 6 commits into
Conversation
…keys Remove the Data Management capability requirement (Download Search Results, View Collectors) from the Search Job API page, keeping only Security (Manage Access Keys). Clarify the Manage Access Keys description in the Role Capabilities doc (create access keys; add Run Log Search to a customized scope). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
JV0812
force-pushed
the
DOCS-1767-role-capabilities-update
branch
from
July 21, 2026 10:17
c590a35 to
d44098b
Compare
Only one capability remains, so change the heading to "Required role capability". Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The customized-scope requirement is API-specific, so move it from the Manage Access Keys capability description to a note on the Search Job API page. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
JV0812
commented
Jul 21, 2026
vikas-sumo
approved these changes
Jul 21, 2026
Collaborator
|
Suggestion: revert the heading back to plural — Every API doc in |
kimsauce
approved these changes
Jul 22, 2026
kimsauce
left a comment
Collaborator
There was a problem hiding this comment.
Approving with the suggestion above to revert the heading back to plural (Required role capabilities) for consistency with other API docs.
kimsauce
reviewed
Jul 22, 2026
Fix cell spacing in the Manage Access Keys row and revert the Required role capabilities heading to plural for consistency with other API docs.
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.
Purpose of this pull request
This pull request updates the required role capabilities for the Search Job API and clarifies the Manage Access Keys capability, per DOCS-1767:
docs/api/search-job.md— remove the Data Management capability requirement (Download Search Results, View Collectors); keep only Security (Manage Access Keys).docs/manage/users-roles/roles/role-capabilities.md— clarify the Manage Access Keys description: it creates access keys, and if the key uses a customized scope, Run Log Search must be added to the scope.Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/DOCS-1767