> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rogeriq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Permissions

Organization roles, API scopes, OAuth scopes, and public endpoint boundaries.

# Permissions

RogerIQ uses different permission models for dashboard users, public API keys, OAuth installs, and public browser endpoints.

## Organization Roles

| Role | Typical use |
| --- | --- |
| Owner | Billing, organization settings, high-risk admin tasks. |
| Admin | Team setup, integrations, project settings, API keys. |
| Agent | Inbox work, replies, contacts, knowledge, normal support operations. |
| Viewer | Read-only access where supported. |

## Public API Scopes

| Scope | Grants |
| --- | --- |
| `read` | Read public API resources. |
| `write` | Mutate public API resources. |
| `admin` | Administrative API access where supported. |

## HolyDocs OAuth Scopes

| Scope | Grants |
| --- | --- |
| `read` | Read project resources. |
| `write` | Mutating project resources. |
| `kb:write` | Knowledge article bulk upsert. |
| `insights:read` | Doc gaps and analytics. |
| `widget:write` | Widget config and proactive trigger. |

## Public Browser Endpoints

Public forms, beacons, and widget endpoints do not use API keys. They are constrained by project IDs, visitor tokens, allowed origins, rate limits, secure identity, and spam controls.