Permissions changedapi/beta/organization/rbac_roles/permissions
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+10added
Lines−8removed
From line
60
where the diff opens
First seen
10 Sep 2026
this site's first read of the page
Recorded edits10to this page, all time
The whole hunk
from line 60, old and new numbered
/
from line 60
6060 The vocabulary follows the resource: an `organization` grant carries a
6161 product-feature entitlement (for example `chat`), an admin-panel
6262 permission entitlement (`permission_*`), or a blanket capability-access
63 mode — `capability_access_all` grants every product-feature entitlement,
64 and `capability_access_all_ga` grants the generally-available subset as
65 it stands at permission-check time; neither mode grants model-access
66 entitlements. A consumer enumerating a role's per-feature grants should
63 mode — `capability_access_all` grants every product-feature entitlement
64 except `inference_hooks_inspection`, which a role holds only through its
65 own row, and `capability_access_all_ga` grants the generally-available
66 subset of those as it stands at permission-check time; neither mode grants
67 model-access entitlements. A consumer enumerating a role's per-feature grants should
6768 treat a blanket row as granting every product-feature entitlement it
6869 covers, or it will under-report the role's effective access. A `connector_tool` grant carries
6970 a tool-access action (`use` or `always_allow`); a `connector_scope` grant
from line 297
296297 The vocabulary follows the resource: an `organization` grant carries a
297298 product-feature entitlement (for example `chat`), an admin-panel
298299 permission entitlement (`permission_*`), or a blanket capability-access
299 mode — `capability_access_all` grants every product-feature entitlement,
300 and `capability_access_all_ga` grants the generally-available subset as
301 it stands at permission-check time; neither mode grants model-access
302 entitlements. A consumer enumerating a role's per-feature grants should
300 mode — `capability_access_all` grants every product-feature entitlement
301 except `inference_hooks_inspection`, which a role holds only through its
302 own row, and `capability_access_all_ga` grants the generally-available
303 subset of those as it stands at permission-check time; neither mode grants
304 model-access entitlements. A consumer enumerating a role's per-feature grants should
303305 treat a blanket row as granting every product-feature entitlement it
304306 covers, or it will under-report the role's effective access. A `connector_tool` grant carries
305307 a tool-access action (`use` or `always_allow`); a `connector_scope` grant
No line in this hunk matches that.