{
  "id": 17603366,
  "title": "Which Sheet Automations Get a Human Approval Step, and Which Just Run?",
  "url": "https://urgent.news/2026/11/01/which-sheet-automations-get-a-human-approval-step-and-which-just-run",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-01T13:13:45.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/hayrullahkar/which-sheet-automations-get-a-human-approval-step-and-which-just-run-1dao"
  },
  "original_language": "en",
  "account": "Every Apps Script job built for a small team faces a critical decision: should it proceed uninterrupted, or should it halt and await human intervention? The consensus within the team is as follows: jobs that read, summarize, format, and solely modify data within the same spreadsheet without resulting in irreversible changes are allowed to run automatically. Conversely, jobs that delete data, send information outside the company, or handle financial transactions must first write a plan and then wait for human review before executing the final steps.\n\nTo illustrate this point, the team conducted a dry run for Workspace offboarding. In this scenario, the reviewer is required to input the leaver's email address before the apply step can be executed. This is due to the ease with which a checkbox can be ticked without proper attention to the plan. The downside of this approval step is clear: every time the person who approves is away, the job idles at this point. Furthermore, a plan that goes unread essentially becomes an inefficient method of repeating the same mistakes.\n\nFor those who manage automations for small teams, the question arises: how do you determine the line between \"just run\" and \"ask first\"? Additionally, who steps in to approve when the usual approver is unavailable? There have been instances where teams have removed approval steps altogether because they deemed the approvers as unengaged and non-reading.",
  "summary": "Every Apps Script job we build for a small team ends with the same argument: should this run straight through, or should it stop and wait for a person? Our current line is roughly this: Runs straight through: reads, summaries, formatting, and anything that only writes inside the same spreadsheet and can be redone by running it again. Writes a plan first, then waits: anything that deletes, sends…",
  "key_points": [
    "Jobs that modify data within spreadsheet can run automatically",
    "Jobs deleting data, sending info outside company need human approval",
    "Approval step creates idle time if approver unavailable"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}