Pixie CRMHelp Centre
Sales & Marketing Hub · Feature guide

Enable or pause the Hub outbound email boundary

Review the connected workspace and explicitly control whether approved queued marketing email may use the existing SMTP transport.

Audience: authorised staffReviewed 13 November 2026

Use these steps in your selected Pixie CRM company workspace. The module, dependent tools and actions available to you follow its configuration and your permissions.

Where to start

Hub → Data & connections → Connected workspace → Enable / Disable delivery

Permission

Manage delivery settings + Publish approved resources

Before you begin

Have the existing workspace sender configuration and your organisation’s delivery requirements checked first. This control enables the Hub’s use of the configured transport; it does not create a new email account.

Follow these steps

  1. Open Connected workspace and inspect the available native tools, adapter status and current outbound setting.
  2. If enabling is appropriate, choose Enable delivery. Read the explanation and tick the explicit authorisation to use the workspace’s configured email transport.
  3. Confirm Enable delivery, then return to the page and check its status.
  4. Keep recipient consent, independent email approval and explicit queueing in the normal workflow; enabling the transport does not replace them.
  5. To pause processing, choose Disable delivery and confirm. Review any messages already in transit separately.

Fields and options

Transport
Uses the workspace’s existing SMTP sender configuration and company identity.
Independent controls
Publishing content and enabling outbound are separate from selecting recipients and queuing an email.
Processing
The existing CRM cron advances eligible queued messages within the module’s bounded delivery limits.

Rules and limits

  • No SMTP username, password or provider setting is edited by this Hub control.
  • Disabling outbound stops processing queued messages while disabled; it cannot recall a message already transmitted.
  • The Hub does not implement external ad-network account setup or social-network publishing itself. Social Media Automation is a separate module.

Check the result

  • Reload Connected workspace and check the intended enabled/disabled state.
  • Confirm enabling alone did not create delivery rows or send content.

If something does not look right

  • If the control is unavailable, check both delivery-settings and publication permissions.
  • If the sender fails, repair it through the original workspace email configuration rather than placing credentials in resource content.

Common questions

Does enabling outbound send every published email?

No. Only explicitly queued eligible deliveries are processed.

Can this screen configure Meta or Google social apps?

No. Social provider configuration belongs to the separate Social Media Automation module.