Who can use this
- Admins and RevOps owners who understand the CRM, Slack, domain, and automation impact of the change.
- Super Admins when pricing context is included.
- Operators can review settings, but broad defaults should be approved by the workspace owner.
Before you start
- Finish CRM connection, CRM properties, pipeline stages, and meeting-title rules first.
- Decide whether the setting should apply to the whole workspace or only to a narrow test path.
- Confirm the relevant integration is connected before changing provider-specific options.
Steps
- Review domain settings, including alternate domains, partnership domains, and alternate email addresses.
- Review CRM deal settings such as CRM email object logging, CRM Slack object logging, draft email CRM logging, preemptive deal creation, amount population, and CRM update sensitivity.
- Review Slack notification toggles for post-meeting and post-email automation notifications.
- Review provider-specific settings only when they apply to your connected CRM, such as HubSpot meeting association or Salesforce CDC sync status.
- If deal qualification settings are available in your workspace, review them with the admin who owns qualification criteria.
- Change one category at a time, then test the affected workflow before changing more settings.
What to expect
- Advanced settings are not required to complete onboarding.
- Some cards appear only for certain CRM providers, roles, feature flags, or connected integrations.
- Most toggles save to the dashboard configuration for the authenticated workspace user or org context and affect downstream automation behavior.
- Disabled or unavailable settings may mean the feature is not enabled, the viewer lacks the right role, or the required integration is not connected.
Common issues
- A setting is changed before the related CRM, Slack, or domain setup is complete.
- A broad CRM setting changes deal creation, amount population, or CRM logging behavior more than expected.
- Domain lists include generic email domains or stale aliases that make account matching less reliable.
- Slack notification toggles are changed without confirming where post-automation notifications should go.
- A provider-specific card is expected but the connected CRM is a different provider.