Skip to main content
Scopes define what your integration is allowed to do when calling the APIs. When creating a token or configuring an authorization flow, you select the scopes your integration needs. These scopes limit access to specific resources or actions, such as reading chats or updating settings. You choose scopes based on what your integration needs to do. For example, if your app only reads data, you can grant read-only scopes. To see which scopes are required for a specific API method, check the method description in the API documentation.

General rules

  • ro means read only
  • rw means read/write
  • rc means read/create
  • all rw scopes contain ro privileges
  • all access scopes contain my privileges
  • all all scopes contain access privileges and my privileges

Accounts scope types

Account scopes

Role scopes

Session scopes

Organization scopes

Text scope types

Agent scopes

Access rules scopes

Bot scopes

Group scopes

Chat scopes

  • Chats conversation data applies to:
    • chat events
    • chat properties
    • thread properties
  • Chats meta data applies to:
    • chat users

Customer scopes

Multicast scopes

Properties scopes

Tag scopes

Webhook scopes

Accessing chat

This chart shows every possible chats scenarios:
  • chats without my access and without my presence (chats -A -P)
  • chats with my access but without my presence (chats +A -P)
  • chats with my presence but without my access (chats -A +P)
  • chats with my access and with my presence (chats +A +P)
The table shows scopes dependency of accessing chat:

Accessing parts of chat

The table shows scopes dependency of accessing chat parts: