Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.319 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One change · api

List RBAC Role Permissions changedapi/beta/organization/rbac_roles/permissions/list

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 58 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 58, old and new numbered
/
lines
from line 58
5858 The vocabulary follows the resource: an `organization` grant carries a
5959 product-feature entitlement (for example `chat`), an admin-panel
6060 permission entitlement (`permission_*`), or a blanket capability-access
61 mode — `capability_access_all` grants every product-feature entitlement,
62 and `capability_access_all_ga` grants the generally-available subset as
63 it stands at permission-check time; neither mode grants model-access
64 entitlements. A consumer enumerating a role's per-feature grants should
61 mode — `capability_access_all` grants every product-feature entitlement
62 except `inference_hooks_inspection`, which a role holds only through its
63 own row, and `capability_access_all_ga` grants the generally-available
64 subset of those as it stands at permission-check time; neither mode grants
65 model-access entitlements. A consumer enumerating a role's per-feature grants should
6566 treat a blanket row as granting every product-feature entitlement it
6667 covers, or it will under-report the role's effective access. A `connector_tool` grant carries
6768 a tool-access action (`use` or `always_allow`); a `connector_scope` grant
Feedback