Monitor and Govern

Users create and edit automations; you govern them. The Monitor page gives Owners and Contributors a view of every automation users created on this agent (what runs, for whom, how it is going) and, within the permission you have been given, the power to pause, resume, disable or delete.

Navigate to Automations → Monitor in the left sidebar.

Automations users set up on this agent — scheduled tasks that run on their own and deliver the result as a new conversation, a WhatsApp message or an email.

The Monitor never edits an automation. Contributors govern; they do not rewrite. What an automation does stays with the user who asked for it.

On this page you find the automation that Rina Wijaya, Kirana's operations lead, created in Atlas's chat: KG-2041 delay / on-hold check. You see how it is going, read its definition and run history, and learn when to pause or disable it.

Before you start

• You are an Owner or Contributor of the agent.
• Automation is switched on in the policy, and users have created automations (Create an Automation).

Who can open it

Reading users' automations is sensitive: they hold people's standing instructions, phone numbers and email addresses. So access is a deliberate grant, decided per contributor.

Without permission the Monitor shows a warning in place of the list and requests nothing else, so a contributor still sees that the feature exists and knows whom to ask.

The three permissions

Set on the agent's Agent Contributors page (Organization → Agents → Contributors). See Managing Agent Access.

Deleting is not one of these: only Organization Owners and Admins can delete from the Monitor.

The summary

At the top, six counts, always visible whatever the privacy mode because they carry no content:

For Atlas, after Rina created her automation and ran it twice with Run now, the counts read: Active automations 1, Paused 0, In error 0, Users with automations 1, Runs today 2, Failed runs today 0.

Browse and search

Below the counts, filters narrow the list:

The table shows Automation, User, Trigger, Schedule, Action, Status, Last Run, Next Run and Created At. Select a row to open its details. Click Apply after changing the filters, and Reset to clear them. For example, choose Rina Wijaya under User to see only her automations, or Error under Status to find the ones that stopped by themselves.

Automation details

A drawer opens on the right, showing:

For Rina's automation, the drawer shows her original instruction, "Every weekday at 7:30, check the status of project KG-2041 and give me a short summary, but only if it is delayed or on hold.", next to what Atlas made of it. The Condition lists the rules under Any of these must hold: project_status contains delayed, or project_status contains on hold. Comparing the two is the quickest way to see whether the agent understood the user.

Execution history

For every run: Scheduled For, Kind (scheduled, run now, retry, catch-up), Status, whether the Condition held, what each Action did (for example Send email: Sent, or Failed with the reason), and how long it took. A failure shows a plain-language reason. See Troubleshooting Runs.

Rina's two test runs both show Run now, Succeeded, Condition Met, and Create conversation: Sent. A scheduled run on a day when KG-2041 is on track would show Condition Not met and no action. That is a normal, successful run.

History records how a run went, not what it said. The result itself is in the user's conversation, which you can only read if you may read that user's conversations.

Governance actions

Buttons at the bottom of the drawer, according to your permission and the automation's status:

Disable is stronger than Pause: use Pause for a temporary stop the user may reverse, and Disable when you do not want the user to bring it back. For example, pause Rina's check while the project status source is being migrated, and tell her so. Disable an automation that sends project details to a WhatsApp number or email address outside Kirana.

Privacy Mode

Privacy Mode has priority over contributor permission. When the organization has it on:

• Each automation's content is stored encrypted: the name, the original instruction, the condition, the task, the skills, the WhatsApp number and the email recipient, plus the creator's name and email.
• Staff see "Hidden — privacy mode" in their place. The list still shows the schedule, action, status and run times, and the summary counts, because those are operational metadata Qlar needs to run the automation.
• Owners and Contributors cannot read the content, whatever they have been granted. Qlar decrypts it only while running the automation, for the user's own benefit.
• Content is not written to run history, error messages or logs.
• The WhatsApp message or email itself still carries the full result, because delivering it is what the user asked for.

Automations are not deleted because of Privacy Mode; they are kept as long as they have future runs, and destroyed with their encryption key when deleted. See Privacy Mode.

Transcripts

Each run happens in a conversation, and the task is sent to the agent as a hidden message. In the CMS conversation pages that message, and the arguments of automation tools, are redacted unless the reader is allowed to view automations. So reading a transcript never becomes a back door to someone's automation.

When the policy changes

The Monitor and the Policy work together. A stricter policy shows up here as automations that were paused or stopped, each with a reason such as "Paused: more active automations than the policy allows" or "Stopped: runs more often than the policy allows".

Check the result

1. In the CMS, open Automations → Monitor for Atlas. The summary shows at least one active automation and one user with automations.
2. The table lists KG-2041 delay / on-hold check with Rina Wijaya as the user, Trigger Time, and Action Create conversation.
3. Select the row. The drawer shows the original instruction, the two project_status rules, and Runs so far. If you have the history permission, Execution history lists each run with its kind, status, condition, and actions.
4. If you see no list but a warning, ask an Organization Owner or Admin to grant you Can view automations.

Next steps

• Next in the journey: Troubleshooting Runs, to learn to read the status reasons and run outcomes.
• Help → Monitor: every field of this page.