Permissions
List RBAC Role Permissions
$ ant beta:organization:rbac-roles:permissions listList the permissions an RBAC Role grants.
Models
beta_rbac_all_connectors_permission_resource: object{ type: "all_connectors" }
Kind of resource the permission applies to.
beta_rbac_connector_permission_resource: object{ type: "connector", connector_id }
Kind of resource the permission applies to.
ID of the connector the permission applies to.
beta_rbac_connector_scope_permission_resource: object{ type: "connector_scope", connector_id, scope }
Kind of resource the permission applies to.
ID of the connector the permission applies to.
scope: stringOAuth scope the permission names — the role may receive this scope when
tokens are minted for the connector.
OAuth scope the permission names — the role may receive this scope when tokens are minted for the connector.
Subject to the same encoding rule as tool_name: a scope containing
characters outside [a-zA-Z0-9_-] (or colliding with a reserved form)
appears server-encoded in a stable {prefix}_{32-hex} form. OAuth
scopes routinely contain : and /, so most appear encoded.
beta_rbac_connector_tool_permission_resource: object{ type: "connector_tool", connector_id, tool_name }
Kind of resource the permission applies to.
ID of the connector the permission applies to.
tool_name: stringPublished name of the connector tool the permission applies to.
Published name of the connector tool the permission applies to.
When the published name contains characters outside [a-zA-Z0-9_-] (or
collides with a reserved form), it is server-encoded into a stable
{prefix}_{32-hex} form — a shortened readable prefix of the name plus
a hash — from which the published name is not recoverable.
beta_rbac_organization_permission_resource: object{ type: "organization", organization_id }
Kind of resource the permission applies to.
UUID of the organization the permission applies to.