RBAC Roles changedapi/beta/organization/rbac_roles
Nearest release: v2.1.315, published under an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+5added
Lines−4removed
From line
267
where the diff opens
First seen
10 Sep 2026
this site's first read of the page
Recorded edits11to this page, all time
The whole hunk
from line 267, old and new numbered
/
from line 267
267267 The vocabulary follows the resource: an `organization` grant carries a
268268 product-feature entitlement (for example `chat`), an admin-panel
269269 permission entitlement (`permission_*`), or a blanket capability-access
270 mode — `capability_access_all` grants every product-feature entitlement,
271 and `capability_access_all_ga` grants the generally-available subset as
272 it stands at permission-check time; neither mode grants model-access
273 entitlements. A consumer enumerating a role's per-feature grants should
270 mode — `capability_access_all` grants every product-feature entitlement
271 except `inference_hooks_inspection`, which a role holds only through its
272 own row, and `capability_access_all_ga` grants the generally-available
273 subset of those as it stands at permission-check time; neither mode grants
274 model-access entitlements. A consumer enumerating a role's per-feature grants should
274275 treat a blanket row as granting every product-feature entitlement it
275276 covers, or it will under-report the role's effective access. A `connector_tool` grant carries
276277 a tool-access action (`use` or `always_allow`); a `connector_scope` grant
No line in this hunk matches that.