Fix horizontal overflow in Roles & Permissions tables - #225
Open
claude[bot] wants to merge 2 commits into
Open
Conversation
The three role tables on the Roles & Permissions page overflowed their content width, hiding the far-right column behind a horizontal scroll. Mintlify markdown tables don't support per-column widths, so this trims verbose cell and label text (keeping status markers and meaning) so the tables fit without scrolling. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RRpcpmRyY3cF1qmUxeyx9j
Contributor
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| docs/orgs-and-projects/roles-and-permissions.mdx | Shortens table wording without changing documented permissions; the previously reported lookup-mapping scope issue is fixed. |
Reviews (2): Last reviewed commit: "Restore "in Lexicon" qualifier on lookup..." | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Greptile flagged that trimming "Map Property to Lookup Table in Lexicon" to "Map Property to Lookup Table" dropped the scope qualifier: local report mappings are available to all roles, while the Lexicon-level mapping is the role-gated one. Restore the qualifier for accuracy; all other table trims stay in place. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RRpcpmRyY3cF1qmUxeyx9j
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
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
1 participant
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.
Requested by Jess Chaidez · Slack thread
Before: On the Roles & Permissions page, the role tables were wider than the content area. The far-right column (Member / Consumer) was cut off behind a horizontal scroll, so readers couldn't see the last role's permissions without scrolling sideways. Long cell text like "✅ Can save only for self" and long row labels like "Add/Modify/Remove Service Accounts to Organization and or Projects" pushed the table past the available width.
After: The verbose cell and label text is trimmed so all three role tables fit within the content width and every column — including the far-right one — is visible without a horizontal scroll. Status markers (✅ / ❌) and the meaning of each cell are unchanged; no rows or columns were removed.
How: Mintlify markdown pipe tables don't support per-column widths, so the reliable fix is to shorten the text. Long prose was trimmed consistently (e.g. "✅ Can save only for self" → "✅ Only for self", "Only the Creator" → "Only Creator", "Organization" → "Org", "Create and View X Reports" → "Create/View X Reports"). No frontmatter/layout change was added — no other page in this repo uses a wide
mode, so that would be non-standard.🤖 Generated with Claude Code
https://claude.ai/code/session_01RRpcpmRyY3cF1qmUxeyx9j
Generated by Claude Code