Setup, access and permissions

Configure emails per cron run

Follow this guide to set survey_send_emails_per_cron_run; the installed default is 100. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM administrators, marketing teams, service managers and authorised staffPermission: AdministratorModule v2.3.0
Jump to steps
Where to goAdmin Area → Setup → Settings → Surveys
Before you start
  • Verify the module is active and use the exact navigation shown above.
  • Use an account with the stated module and core CRM permissions.
  • Use known test records when changing statuses, visibility, saved filters or global navigation.

What you’ll accomplish

Set survey_send_emails_per_cron_run; the installed default is 100. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Follow these steps

  1. Go to Admin Area → Setup → Settings → Surveys.
  2. Select the record or action required for configure emails per cron run.
  3. Complete the displayed fields and choices described in this guide.
  4. Save, submit, approve or confirm the action as shown on screen.
  5. Refresh the relevant list, record or report and verify the expected result.

Fields and options to review

WorkspaceAdmin Area → Setup → Settings → Surveys
ActionSet survey_send_emails_per_cron_run; the installed default is 100.

Rules the system enforces

  • Only controls rendered by the supplied module are documented; hidden AJAX helpers are mapped to their visible parent workflow.
  • Core CRM record permissions and module permissions are both enforced where the code checks them.

How to confirm it worked

  • The configure emails per cron run action completes without a validation or permission error.
  • The affected record, stock balance, response, session or style reflects the saved state.
  • Audit, notification, report or portal evidence appears only where the module code creates it.

Security, privacy and operational checks

  • Use a controlled test record before applying changes to live inventory, recipients, visitor tracking or global styling.
  • Grant only the minimum module and core CRM capabilities needed for the task.