Browse, connect, and manage every CRM integration from a unified hub
Open Settings > Integrations for a single hub that lists every catalog integration with a real brand logo, live connection status, and a slide-in detail panel. Search, filter by category, or click a card to connect, manage, or read about what an integration does.
Where the hub lives and how to navigate it.
?integration=<id> (e.g. /settings/integrations?integration=docusign) — the drawer opens on page load.Click a card to open the drawer, then click Connect.
Some integrations are personal; most affect the whole organization.
Every catalog card carries an installation scope— visible in the drawer's header subtitle:
integrations.connect permission.What each badge means.
Per-user: from the drawer. Org-wide: from the per-provider page.
For per-user integrations (Google Workspace, Microsoft 365, Google Drive, OneDrive) the Disconnect button is built into the drawer — confirm the action and the connection ends immediately. Already-synced data (email metadata, calendar event metadata, linked-file references) is purged from Laureo, but your actual emails, calendar, and files stay on the provider side.
For org-wide integrations the drawer hands off to the per-provider settings page via the Manage advanced settings →link — that's where the disconnect / remove-credentials button lives. Each provider has its own cleanup nuances (e.g., DocuSign tears down envelope webhooks, Slack stops broadcasts but keeps the channel mapping for one re-connection cycle).
Who can connect, configure, or disconnect each integration.
integrations.connect — gates the Connectbutton on org-wide cards. Without it, the button is disabled and a tooltip explains you need to ask an admin. Per-user cards (Google Workspace, Microsoft 365, Drive, OneDrive) bypass this — each seat can always connect their own account.integrations.configure — gates the Manage advanced settings → link and the Disconnectbutton on org-wide cards. Required to change credentials, webhook secrets, field mappings, or to disconnect an org-wide integration.messaging.send_sms / messaging.send_voice / messaging.send_whatsapp — per-seat permission to actually useTwilio / WhatsApp for outbound messaging on entity pages. Connecting Twilio is a one-time admin action; sending happens under each seat's messaging permission.documents.send — per-seat permission to send an envelope through DocuSign or PandaDoc.sync.trigger— per-seat permission to fire the manual “Sync now” button on the per-provider settings pages.messaging.send_* + documents.send + sync.trigger but not the org-level integrations.* gates, and sales_rep / marketing / service have none of the org-level connect / configure gates by default. Override any of them per role on Admin > Roles & Permissions.Per-user OAuth covering email push sync, two-way calendar sync, scope-minimized Drive access, and Meet transcript auto-link.
drive.filescope. You browse your Drive inside Google's own picker UI, and the CRM only gains access to the specific files you select — never your full Drive. This is the pattern Google recommends for minimizing OAuth scope exposure.Per-user OAuth covering mail, calendar, contacts, tasks, OneDrive files, Teams meeting links, and out-of-office indicators.
/me/messages. Send, archive, trash, reply.Microsoft Teams channel broadcasts (Deal Won, New Lead, etc.) are configured separately on the Microsoft Teams integration card — see below.
Org-channel notifications powered by an incoming webhook URL.
Configure a Slack incoming webhook or a Microsoft Teams workflow URL on the corresponding integration card, then toggle on the events your team wants broadcast. Ten CRM event types are supported:
Capture page views from your WordPress site as CRM activities — securely.
The WordPress integration is configured under a dedicated settings page at Settings > Integrations > WordPress. Each WordPress site you want to track registers separately and receives its own tracking key + HMAC secret. Events are signed on your WordPress server with an HMAC secret that never leaves the server — visitors cannot read it from page source.
See WordPress integration for the full step-by-step registration and plugin install guide.
<script> tag on your WordPress page. That approach exposed the key to anyone viewing the page source. The v2 integration replaces it with site-scoped tracking keys + a server-side HMAC secret. If you had the old script tag installed, register each site under the new flow.SPF, DKIM, and DMARC for reliable outbound email delivery.
Configure domain verification to improve email deliverability and establish trust with email providers. The following DNS records must be configured: