Privacy and security are gaining in importance as technology takes over the world. More systems get interconnected every day, exchanging streams of data between each other. It is important, in that regard, that integrations only have access to the data they require to operate.

Some integrations, for instance, may only need to send messages on your behalf: in this case, they should not even have the permission to read your messages. We would give them the scope website:conversation:messages with write permissions.

If any of those integration tokens were to leak and be re-used by hackers, no data would be put at risk, as the token scopes are not broad enough!

• QuickstartGet introduced on how to build Crisp plugins.Read
• SubmissionsLearn how to submit your integration for review.Read

Available Scopes

Multiple granular scopes are available, each one with associated read or write permissions.

Depending on the REST API route that you need to access, or the RTM API event that you want to receive, you will need to request certain scopes.

All available scopes are listed in this table:

Considerations

Submission review process

As we want to ensure each integration with Crisp uses subscribed website data in a fair and privacy-first way, you need to request scopes through our submission review process over the Marketplace.

Whenever requesting scopes, you are prompted to choose its permission level, from read-only, to both read and write, or even write-only (where this is relevant).

Then, we ask that you explain why do you need this scope (ie. to do what, what do you intend to build with this scope?).