chore: clarify rbac example#2548
Conversation
There was a problem hiding this comment.
Pull request overview
Clarifies the RBAC guide for Ory Keto by improving how the OPL schema is referenced and expanding guidance around scoping/object IDs to avoid cross-tenant collisions.
Changes:
- Replaces the plain “OPL schema” mention with an explicit link to the Ory Permission Language reference.
- Adds a new “Object ID guidance” section explaining object ID collision risks and recommended ID formats.
- Removes the older “Role ID guidance” section later in the document in favor of the earlier, expanded guidance.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
📝 WalkthroughWalkthroughThe ChangesSidebar Navigation Structure
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Improve RoleID Guidance and Scoping explanations in Keto RBAC Guide
Summary by CodeRabbit