Policy
Open in CMSThe Automation Policy screen decides whether users of this agent may set up automations, and within which limits. Found in the agent sidebar under Automations → Policy.
Purpose and Access
| Automation Policy | Decides whether the users of this agent may set up automations — tasks the agent runs on a schedule for them — and within which limits. |
| Page Access | Agent Owners and Contributors. |
| Applies | At once when saved, without publishing the agent. |
| Checked | When an automation is created or changed, and again at every run — so a tighter policy binds automations made under a looser one. |
| Default | Off. Until someone switches it on, the agent offers no automations. |
Master Switch
| Let users create automations on this agent | Off by default. While off, the agent offers no automations and existing ones are skipped when due — nothing is deleted. On lets users ask the agent to run a task on a schedule and deliver the result as a new conversation, a WhatsApp message or an email. |
What Users May Automate
| Allowed Triggers | Multi-select. Only Time (schedules) is available; event triggers are not available yet. At least one is required. |
| Minimum Interval (minutes) | The shortest gap allowed between two runs of one automation. 5–10080, default 15. Automations that run more often are stopped. |
| Allowed Actions | Multi-select: Create conversation, Send WhatsApp message, Send email. At least one is required. WhatsApp goes to the number the user gives, from this agent's own WhatsApp number (a channel on the public or private server in the Published configuration). Email goes to the address the user gives (or their account's address), from {agent}-automation@qlar.ai under this agent's name; nobody reads that mailbox. A policy saved before email existed has Send email unticked until a contributor ticks it and saves. |
| Maximum WhatsApp Messages per Day | For all of this agent's users together. 1–5000, default 100. Protects this agent's WhatsApp number from being blocked. Applies only while WhatsApp is an allowed action. |
| Maximum Emails per Day | For all of this agent's users together. 1–5000, default 100. Protects the sending domain from being marked as spam. Applies only while email is an allowed action. Separately, a user's automations may send at most 10 emails an hour to one address, checked when an automation is created or changed. |
| WhatsApp channel notice | Shown while Send WhatsApp message is allowed and the Published configuration cannot send it: no WhatsApp channel, a channel on Meta Cloud, Coster or Qontak (warning), or a channel that is switched off (info). |
Limits per User
| Maximum Active Automations | Running at the same time. 1–100, default 10. Lowering it pauses the newest ones above the limit. |
| Maximum Total Automations | Active and paused together. Up to 200, default 20. Cannot be lower than the active limit. Finished ones do not count. |
| Maximum Runs per User per Day | All of one user's automations on this agent together. 1–1000, default 100. Every run spends credit. |
| Maximum Runs per Automation | 0 means no limit, up to 100000. An automation that reaches it is finished. |
Running
| Run Timeout (seconds) | How long one run may take. 60–900, default 300. |
| History Retention (days) | How long run history is kept. 1–365, default 30. |
| Maximum Retries | Retries after a temporary failure. 0–5, default 2. A WhatsApp message or email is never sent twice; an email is never retried. |
| Retry Interval (minutes) | The wait before a retry. 1–1440, default 5. |
What Users May Do
Six switches, all on by default, for users' own automations.
| Create automations | Off stops new automations; existing ones keep running. |
| Edit automations | Change the schedule, task, condition, actions or recipient. |
| Delete automations | Off leaves users only able to pause. Owners and Admins can still delete from the Monitor. |
| Pause and resume | Stop an automation for a while and start it again. |
| Run now | Run an automation immediately instead of waiting for its schedule. |
| View history | See when each automation ran and how it ended. |
| Contributors | Not limited by these switches — they govern every automation from the Monitor. |
Save and Sync
| Last Changed | Shows when the policy was last saved. |
| Save | Validates every field with the same rules the server uses, and shows the problem beside the field. |
| Conversation service status | Conversation service: up to date: the chat service has the latest policy. Conversation service has not received the latest policy: a warning with a Resend button that sends it again. Could not check the conversation service: an informational note. |
Related guide: Set Up the Automation Policy