PermissionService
Chatto exposes this service below /api/connect.
Shared message and enum definitions are documented in Shared Types And Enums.
PermissionService
Section titled “PermissionService”Read-only effective authority. Configuration and explanations remain in chatto.admin.v1.AdminPermissionService.
ListEffectivePermissions
Section titled “ListEffectivePermissions”Any authenticated member may read a bot’s effective permissions. Human targets require user.manage-permissions, including self-targeted reads. Bot authority includes the owner’s current limits. Hidden room identities, stored grants, credentials, and individual DM participants are not exposed. Missing or deleted targets return NOT_FOUND. Each call returns the complete visible set from one coherent read, without pagination or truncation. Clients should refresh visible views (the bundled client uses 30 seconds) and clear the view on close or read failure.
POST /api/connect/chatto.api.v1.PermissionService/ListEffectivePermissionsInput: ListEffectivePermissionsRequest
Section titled “Input: ListEffectivePermissionsRequest”Read all effective permissions for one account.
| Field | Type | Description |
|---|---|---|
user_id | string | Required target account ID. |
Result: ListEffectivePermissionsResponse
Section titled “Result: ListEffectivePermissionsResponse”All visible effective grants in permission-catalog order, then stable scope-ID order. Denied and unconfigured permissions are absent. Inherited and included permissions remain separate entries; clients can group them for display.
| Field | Type | Description |
|---|---|---|
permissions | repeated EffectivePermission | Effective grants visible to the caller. |