docs: add AI Risk Hub permissions to roles table and hub docs#2691
Conversation
|
Overall readability score: 54.23 (🟢 +0)
View detailed metrics🟢 - Shows an increase in readability
Averages:
View metric targets
|
Up to standards ✅🟢 Issues
|
There was a problem hiding this comment.
Code Review
This pull request updates the documentation regarding the AI Risk Hub access permissions, roles, and Software Composition Analysis (SCA) daily re-scan requirements. Specifically, it introduces a table mapping AI Risk Hub tab access to roles, updates the SCA findings behavior explanation, details the requirements for proactive SCA scanning using Trivy, and updates the role-and-permission tables for GitHub, GitLab, and Bitbucket. The review feedback suggests minor copy-editing improvements to enhance readability, such as splitting a long sentence regarding SCA findings and avoiding repetitive phrasing in the Trivy configuration instructions.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Documents which tabs are accessible per role: Overview is available to all organization members; AI assets and Tools & workflows require organization manager or admin role. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
884c1f1 to
4f3f50f
Compare
There was a problem hiding this comment.
Pull Request Overview
The documentation updates are up to standards and align with the specified requirements for AI Risk Hub role permissions. The changes correctly reflect the differentiated access levels across GitHub, GitLab, and Bitbucket integration tables. No blockers or security concerns were identified, and the implementation of the introductory table in the AI Risk Hub documentation satisfies the requested structural changes.
Test suggestions
- Verify the 'Access AI Risk Hub Overview' row is correctly added and populated in the GitHub permissions table.
- Verify the 'Access AI Risk Hub Overview' row is correctly added and populated in the GitLab permissions table.
- Verify the 'Access AI Risk Hub Overview' row is correctly added and populated in the Bitbucket permissions table.
- Verify the 'Access AI Risk Hub AI assets and Tools & workflows' row is restricted to managers/admins across all provider tables.
- Verify the AI Risk Hub intro table displays correct roles and contains functional anchor links for Overview, AI Assets, and Tools & Workflows.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify the 'Access AI Risk Hub Overview' row is correctly added and populated in the GitHub permissions table.
2. Verify the 'Access AI Risk Hub Overview' row is correctly added and populated in the GitLab permissions table.
3. Verify the 'Access AI Risk Hub Overview' row is correctly added and populated in the Bitbucket permissions table.
4. Verify the 'Access AI Risk Hub AI assets and Tools & workflows' row is restricted to managers/admins across all provider tables.
5. Verify the AI Risk Hub intro table displays correct roles and contains functional anchor links for Overview, AI Assets, and Tools & Workflows.
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
Summary
Context
Resolves OD-164 — confirmed expected behavior:
Test plan
🤖 Generated with Claude Code