Skip to content

Products

Compliance Officer Service Expert-led compliance, end to end Compliance Portal Share security documents securely Access Review Monitor user access across all your systems AI Agents Your compliance program, inside your AI agent Open-source platform Deploy Probo on your own infrastructure

Resources

Probo stories How teams get compliant with Probo Blog Ideas and guidance from the Probo team Guides & tools Practical compliance guides and free tools Love from Customers What customers say about working with Probo Changelog Latest product updates Download Get the Probo Agent

Company

About The people and vision powering Probo Careers Join the team building Probo Brand assets Official logos and visual resources Security Review our security and compliance posture
Overview Understand Probo and its core concepts Product Explore Probo's GRC capabilities Developers Explore GraphQL, CLI, MCP, n8n, and webhooks Deployment Probo Cloud, self-hosting, and configuration

Explore

GitHub Explore our open-source compliance tools

Crisp

Connect Crisp as an access review source by installing the Probo Access Review plugin from Probo, then approving it on the Crisp website you want to review.

View as Markdown

Probo reads your Crisp website’s operators (your team members, not your visitors) through the Crisp plugin API so you can review who has access.

  • Probo organization administrator access
  • Access to the Crisp website you want to review, with rights to install a plugin on it (Crisp operators are either Owner or Member)
  • A Crisp account you are already signed in to, so the approval screen can list the websites you can choose from

The Probo column lists every field shown in the review. The Crisp column shows the operator field Probo reads or marks a field as Not supported when Crisp does not provide it. Probo also records each operator’s job title from title.

Probo fieldCrisp fieldNotes
Namefirst_name and last_nameFalls back to the email
EmailemailAn operator with no email is skipped
Roleroleowner becomes Owner and member becomes Member, ignoring case. Any other value is kept as sent, after trimming. A blank role yields none
AdminroleFlagged as an administrator when role is owner
StatusNot supported
MFAhas_tokenEnabled when true, Disabled when false, Unknown when absent
Last loginNot supported
External IDuser_idStable identifier used to track the account across reviews
Created atNot supported

Probo lists joined operators only. Operators who were invited but have not accepted, and Crisp Marketplace plugin developers attached to the website, both come back from the same Crisp endpoint, and Probo leaves them out of the review.

  1. In Probo, go to Access Review > Connections.
  2. Find Crisp and click App Install.

Probo sends you to Crisp without opening a dialog or asking you for a value.

  1. Crisp shows Link Crisp with Probo Access Review. Click Continue.
  2. Choose the website you want Probo to review.
  3. Crisp installs the Probo Access Review plugin and returns you to Probo.

Finish signed in to the same Probo account that started the connection, with a session that is still valid. Probo ties the installation link to the person who started it, so returning as anyone else is refused. Staying in the same browser is the simplest way to meet that, though it is the account that matters, not the browser.

Probo checks the installation with Crisp. It then names the source after your Crisp website and pulls its operators into your campaigns. The installation link works once, so start again from Probo if you need to connect another website.

Each entry quotes the message Probo shows on the connections page after a failed installation.

  • “This installation link was already used. Start the connection again from Probo.” Each installation link works only once. Return to Access Review > Connections and click App Install again.
  • “The installation could not be verified. Start the connection again from Probo.” Crisp did not confirm the installation for that website. Click App Install again and approve the plugin on the website you want to review.
  • “The provider could not be reached to verify the installation. Please try again in a moment.” Probo could not reach Crisp to confirm the installation, usually because Crisp was busy or briefly unavailable. Nothing was spent, so click App Install again. If the same message keeps appearing, Probo’s own Crisp credential may need attention, so contact your Probo administrator.
  • “Something went wrong while finishing the installation. Please try again.” Probo could not save the connection. Click App Install again, and contact your Probo administrator if it persists.
  • “You no longer have permission to connect this provider for this organization.” Your access to this organization changed while you were in Crisp. Ask an administrator to restore it, then start again from Probo.
  • An authorization error instead of the connections page. Probo refused the return trip because you came back as a different account, your session had expired, or your permission was withdrawn before Crisp sent you back. Sign in again as the account that started the connection and click App Install again.
  • “invalid connector install callback”. The installation link was malformed or more than ten minutes old. Start again from Probo.
  • Crisp is not listed in Connections. The connector is enabled per deployment. Contact your Probo administrator if Crisp does not appear.
  • No operators appear. Confirm you approved the plugin on the website you meant to review. Operators are read when a campaign that includes the Crisp source runs, so add the source to a campaign and start it. Probo lists operators (agents), not visitors.