Статьи по теме: Developers

How do Plugin permissions work

Learn what Crisp plugin permissions mean and how they help you understand what a plugin can access or modify.

Plugins can extend Crisp with integrations, marketplace apps, and custom workflows. Some plugins need to read or write Crisp data to work properly, so permissions make the requested access visible before a plugin is installed.

Plugin permissions shown in Crisp

Why plugin permissions matter

Plugin permissions help you understand what a plugin can do with your workspace data. A simple plugin may only need to store contact data, while a more advanced integration may need to read messages, send replies, or update conversation states.

Community-built plugins are reviewed before publication. Plugin developers must explicitly request the permissions they need, and each requested permission must be justified during review.

Plugin developers do not receive broad access to workspace data by default. Permissions are requested in narrow scopes and can be granted in `read`, `write`, or both modes depending on what the plugin needs to do.

Permission groups

Plugin permissions are grouped into Messaging, Contacts, and Website permissions. Together, they describe access to the Crisp Inbox, Crisp CRM, and workspace-level data.

Messaging permissions

Messaging permissions can include:

`website:conversation:initiate` → create new conversations
`website:conversation:sessions` → access conversation metadata, such as email addresses
`website:conversation:suggest` → suggest conversation information, such as segments
`website:conversation:messages` → access conversation messages
`website:conversation:states` → manage conversation states, such as resolved or unresolved
`website:conversation:participants` → manage conversation participants, such as CC'ed people
`website:conversation:pages` → access browsed pages
`website:conversation:events` → list and push conversation events
`website:conversation:actions` → perform conversation actions, such as sending a transcript
`website:conversation:browsing` → access MagicBrowse
`website:conversation:calls` → access Crisp calls
`website:conversation:reminders` → schedule reminders on conversations
`website:conversation:routing` → manage assigned operators on conversations

Contacts permissions

Contacts permissions can include:

`website:people:statistics` → access CRM statistics, such as the number of contacts
`website:people:suggest` → suggest CRM information, such as segments
`website:people:profiles` → access people profiles
`website:people:conversations` → list conversations attached to a profile
`website:people:events` → list and push CRM events
`website:people:data` → list and set CRM data
`website:people:subscriptions` → manage email subscription status

Website permissions

Website permissions can include:

`bucket:url` → upload files
`website:availability` → access workspace availability data, such as online operators
`website:operators` → manage workspace operators
`website:settings` → manage workspace settings
`website:verify` → access verify-protected information, such as the chatbox signature key
`website:visitors` → access website visitors

Последнее изменение: 05/05/2026

Была ли эта статья полезна?

Спасибо!