Process Automation · Part 6 of 7
Learning series
Process Automation: From Manual Task to Running Workflow- 1Process Automation: Where Should Your Business Start?
- 2Process Mapping Before Automation: Draw It as It Runs
- 3Automating Internal Approvals: A Path and a Deadline
- 4Manual Data Entry: When the System Reads the Document
- 5Connecting Your Systems: The End of Copy and Paste
- 6Automation Controls: Logs, Permissions and Data Protection (you are here)
- 7A 90-Day Plan to Automate Your Business Processes
Controlling process automation means knowing 5 things about every automation in your business: what it did and when, who may change it, who owns it, who is alerted when it breaks, and how work continues by hand if it stops. In part 5 of the series you connected your systems, so data now moves on its own. This sixth part of 7 answers the next question: who watches what runs by itself? You leave with 5 controls for every automation, what 3 articles of the Personal Data Protection Law say when an automation carries people's data, and an exercise to list every automation and shared account running today.
Why automation needs controls
An automation acts in the company's name: it messages a customer, approves a request within a limit, or moves an employee's details from one program to another. The person who used to do this by hand was naturally watched by colleagues and a manager; an automation works at night and on holidays with nobody seeing it. Over time, situations like these appear:
- An automation built by someone who has left: it still runs, and nobody knows where its settings are or exactly what it does.
- A shared account: one password known to several people, so you cannot tell who changed a step in the workflow.
- A silent stop: an integration stopped days ago, and nobody noticed until a customer complained.
- Data leaving without your knowledge: an online tool that customer or employee data passes through, and you do not know where it stores it.
None of this means automation is a mistake. It means automation needs the same controls you set for any employee acting on your behalf.
5 controls for every automation
- A run log: a record of every time the automation ran: when it started, on which record or request, the result, and the error if any. Without it you cannot answer a simple question such as: was this message actually sent?
- Permissions to change it: decide who can edit or pause a workflow and who may only view its results, and record every change under the name of the person who made it. We explained permissions once data leaves files in Permissions: Who Sees What Once Data Leaves the File. The same principle applies to automation: each person has an account in their own name, never a shared one.
- An owner for every automation: a named person in the business, not necessarily whoever built it, who knows what it does and why, decides whether to change or stop it, and has a named stand-in when away.
- An alert when it fails: a message to the automation's owner as soon as it stops or keeps failing, not after someone finds the damage at month end.
- A written manual fallback: short steps the team knows so work continues by hand if the automation stops, including how to re-enter what was missed when it returns. This extends the approval paths you built in Automating Internal Approvals: a request must not be lost because the system was down for an hour.
What the Personal Data Protection Law says
When an automation carries customer names, mobile numbers or employee details, it is processing personal data. The Personal Data Protection Law published on the SDAIA site has 3 articles that apply directly here:
- Article 19: the controller must take the necessary organizational, administrative and technical measures and means to ensure the protection of personal data, including when it is transferred, in accordance with the provisions and controls set by the regulations. Run logs, permissions and a named owner are among those measures.
- Article 29: it allows personal data to be transferred outside the Kingdom for specific purposes, under conditions that include that the transfer does not prejudice national security or the Kingdom's vital interests, that an adequate level of protection exists abroad, and that the transfer is limited to the minimum personal data needed. This concerns you if your automation or AI tool runs on servers outside the Kingdom.
- Article 31: the controller must keep records of personal data processing activities for a period set by the regulations, containing at least 6 items: the controller's contact details, the purpose of processing, a description of the categories of data subjects, any party the data was disclosed to, whether it was transferred outside the Kingdom, and the expected retention period.
The details these articles leave to the regulations are in the Implementing Regulation on the SDAIA site, and for the full picture of the law see Saudi Personal Data Protection Law (PDPL): A Practical Guide for Businesses. Confirm how they apply to your case with SDAIA or a lawyer; this is not legal advice.
The Origami view
We are a Saudi technology company that builds systems, apps, integrations and AI solutions. When we build an automation, we build its run log, permissions and alerts with it from day one, because adding them after the first problem is far harder than designing them at the start.
Before choosing any tool we ask: where does the data pass and where is it stored? If it carries personal data, the server's location is a decision the owner makes knowingly, not a technical detail discovered later. You will find the details of what we build on our services page.
Exercise: the automation and shared account inventory
Over one week, ask each department to list every automation, integration or tool that runs on its own, and every account used by more than one person, in a table of 6 columns:
- The automation's name and what it does in one sentence.
- Its owner today, and who stands in for them.
- Who can change it, and whether they sign in with a personal or a shared account.
- Where its data goes: which programs, and whether the tool runs on servers outside the Kingdom.
- Whether it carries personal data, such as customer names or employee details.
- Whether it has a run log, an alert and a manual fallback.
Every row with no owner, a shared account, or personal data leaving for a place you do not know is the first thing to fix. The same table is a good start for the record of processing activities Article 31 requires.
In the next part
After 6 parts you have all the pieces: choosing the process, mapping it, approvals, reading documents, integration and controls. Part 7, the final part, A 90-Day Plan to Automate Your Business Processes, puts these pieces in 3 blocks of 30 days and states which decisions belong to the owner and which to the operations lead.
Sources
- Personal Data Protection Law — Saudi Data and Artificial Intelligence Authority (SDAIA) — Article 19 on organizational, administrative and technical measures, Article 29 on transfers outside the Kingdom, and Article 31 on records of processing activities.
- Implementing Regulation of the Personal Data Protection Law — SDAIA
Frequently asked questions
What does controlling automation mean?
Every automation has a run log of what it did and when, permissions that set who can change it, a named owner, an alert when it fails, and a written manual fallback so work continues if it stops.
Why is a shared account in automation tools a problem?
You cannot tell who changed or paused a step in the workflow, and you cannot remove one person's access without changing the password for everyone, so each person should have an account in their own name.
Does the Personal Data Protection Law apply to automation?
Yes, if it carries personal data such as customer names or mobile numbers. Article 19 requires organizational, administrative and technical measures to protect it, including during transfer, and Article 31 requires records of processing activities. Confirm with SDAIA or a lawyer.
Does it matter where an automation or AI tool runs?
Yes, if it carries personal data. Article 29 sets conditions for transfers outside the Kingdom, including an adequate level of protection abroad and limiting the transfer to the minimum data needed.







