Skip to main content
Product screenshot showing CRM properties, pipeline stages, and sync checks. Use stage controls when you need to govern how stages can be used, changed, or written back. Treat these as admin settings because broad stage behavior affects the Deals board and CRM update paths.

​
Who can use this

  • RevOps, sales operations, CRM owners, and admins with CRM permissions.

​
Before you start

  • Use a CRM account that can read and update the fields Ergo needs.
  • Map properties, pipelines, and stages before enabling broad CRM automation.
  • Test changes on one record before rolling them out.

​
Steps

  • Confirm which users should edit stages or stage descriptions.
  • Confirm whether stage changes should write to the connected CRM.
  • Review allowed stage actions with sales operations.
  • Test a stage move on one record before enabling broader use.

​
What to expect

  • Stage controls depend on CRM permissions and the current pipeline configuration.
  • Controls can prevent unsafe updates, but they do not repair stale CRM mappings by themselves.
  • Changes should be coordinated with stage descriptions and restrict-to-pipeline settings.

​
Common issues

  • A user can move a deal in the board but the CRM rejects the stage update.
  • Stage settings changed without retesting permissions.
  • The selected pipeline does not match the intended automation scope.
Last modified on June 8, 2026