Skip to content

Add project-level invite permission callout to Roles & Permissions page - #229

Open
claude[bot] wants to merge 1 commit into
mainfrom
add-project-invite-callout
Open

Add project-level invite permission callout to Roles & Permissions page#229
claude[bot] wants to merge 1 commit into
mainfrom
add-project-invite-callout

Conversation

@claude

@claude claude Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Requested by Ross Gonsolvis · Slack thread

Before: the page's only invite callout is org-level, implying you need an org admin/owner role to invite users anywhere.
After: a project-level callout above the "Invite Users to a Project" section clarifies that a project admin or owner role is enough to invite users to a project.

How: inserted a <Note> callout directly above the #### Invite Users to a Project heading in docs/orgs-and-projects/roles-and-permissions.mdx.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MATNpNajLLqDCoSa6dDhMu


Generated by Claude Code

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MATNpNajLLqDCoSa6dDhMu
@claude
claude Bot requested a review from a team as a code owner September 7, 2026 11:56
@claude
claude Bot requested a review from mbocianski September 7, 2026 11:56
@mintlify

mintlify Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
mixpanel-docs 🟢 Ready View Preview Sep 7, 2026, 11:59 AM

@greptile-apps

greptile-apps Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Confidence Score: 4/5

The PR should not merge until the conflicting organization-level invitation guidance is corrected.

The added callout matches the permission table, but it directly contradicts an earlier callout about the same project invitation action.

Files Needing Attention: docs/orgs-and-projects/roles-and-permissions.mdx

Important Files Changed

Filename Overview
docs/orgs-and-projects/roles-and-permissions.mdx Adds accurate project invite guidance but leaves a conflicting organization-role requirement earlier on the page.

Reviews (1): Last reviewed commit: "Add project-level invite permission call..." | Re-trigger Greptile

</Frame>

<Note>
To invite a user to a project, you need at least an admin or owner role for that project.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Conflicting invite role requirements

This callout says a project Admin or Owner can invite project users, while the existing callout at line 10 says the same action requires an Organization Admin or Owner. The permission table supports the new project-level requirement, but leaving both statements makes readers unsure which role is sufficient. Please narrow the earlier callout to organization-level invitations.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant