Türkiye limits workplace e-mail monitoring; agents get your own guardrails

One question runs through this week: on whose behalf is a system acting, what is it looking at, and who allowed it? Türkiye’s data protection authority answered that for employee communications, while UiPath and Google shipped their own answers for agents. A short window, five days, but it includes an Official Gazette decision that reaches straight into automation design.

KVKK: a principle decision on monitoring workplace e-mail and communication channels

Official Gazette of Türkiye · 8 October 2026 (Board decision of 16 September 2026, No. 2026/2035)

Türkiye’s Personal Data Protection Board published a 16-point principle decision on how employers may monitor corporate e-mail and other channels used for work. It isn’t limited to e-mail: internal messaging, CRM and ticketing systems, and chat and recording areas in meeting platforms are named too. Processing only traffic and log records, without opening content, still counts as processing personal data. A generic “your mailbox may be monitored” notice does not meet the duty to inform; the notice has to say concretely whether logs or content will be reviewed, when content may be accessed, and how long data is kept. Monitoring through tools that record everything an employee does, indiscriminately, is treated as unlawful. Access to the collected data should be limited to authorised staff and logged.

Why it matters. It reads like an HR policy document, but automation teams are squarely in scope. A robot reading a shared mailbox, an agent watching Teams channels, or a task-mining tool recording every click on a desktop all operate in exactly these channels. My reading: “record everything and filter later” is no longer a defensible design. This week I’d check two things: the list of mailboxes and channels your robots and agents read, and who can see the logs and recordings those tools produce. If there’s no list, the privacy notice is probably incomplete as well. This isn’t legal advice; read the text with your legal team.

UiPath Agents: review by Autopilot and bring-your-own guardrails

UiPath Documentation · 1 and 8 October 2026

Agent review, in preview since 8 October, replaces the old Agent score. Autopilot reviews an agent, lists critical issues, warnings and improvements, grades it from A to F by the number and severity of issues, and can apply the fixes in the same conversation. On 1 October, also in preview, organisations gained the option to add their own safety-vendor subscription to the AI Trust Layer and use it for agent guardrails. Supported providers during preview are Azure AI Language, Azure Content Safety and Noma. Each detection appears in the agent trace with the provider that produced it, and a guardrail can fall back to its UiPath-managed equivalent if the provider can’t be reached.

Why it matters. Using your own guardrail subscription means the content filters your security team already approved can follow you into agents, which may shorten sign-off. Watch the fallback behaviour, though: which rule applies while the provider is down will be one of the first audit questions, and that should be a written policy decision. I’d treat the A–F grade as preparation for code review rather than a quality gate. A good grade shortens the review; it doesn’t replace it.

Orchestrator: enforced tenant encryption and Maestro Flow identity

UiPath Documentation · 7 and 12 October 2026

Since 7 October, Orchestrator tenants can turn on enforced encryption: job, job event, robot log, queue item and storage bucket data are encrypted at rest with a KMS key. You enable it through your technical account manager or UiPath Support, and encrypted fields can’t be searched. The 12 October notes add a trace ID in job fault details when a robot fails to fetch credentials, and Maestro Flow node jobs without a named robot now run under the caller’s identity. Separately, the Automation Cloud notes of 6 October say allowlisting Cloudflare’s 104.16.0.0/13 range may be needed for any UiPath service, not only Document Understanding; UiPath recommends DNS-based allowlisting where possible.

Why it matters. Encryption is a concrete answer to one of the most common objections to cloud Orchestrator in banking and insurance. The cost is just as concrete: you lose search on encrypted fields. If operations staff look up queue items by reference, talk about that habit before switching it on. The Maestro Flow identity change looks small but alters the permission model, because the audit trail will now show a different identity doing the work. And if your network restricts outbound traffic, the Cloudflare note may be the most practical item this week.

Google Cloud: the Gemini agent, “one agent for work”

Google Cloud Blog · 8 October 2026

At Gemini at Work 2026, Google Cloud introduced a single agent that answers questions, does knowledge work, creates images and writes and runs code. It runs persistently in the cloud, carries on with long jobs after the user closes the laptop, and can orchestrate both Gemini and Anthropic’s Claude models. Each agent gets a cryptographically attested identity with least-privilege permissions; actions land in an audit trail attributed to the agent rather than a person, traffic passes through Agent Gateway, and spend caps can be set per project. It can connect to MCP servers inside or outside the company network. Financial services and legal editions are in preview; the post gives no availability date, edition or price for the agent overall.

Why it matters. An “agent coworker” with its own identity, mailbox and spending cap is the latest version of the RPA robot-account debate. The identity and audit design points the right way. My question is different: when one process involves a UiPath robot, a Copilot flow and a Gemini agent, who keeps the end-to-end trace? I wouldn’t open a budget line before availability dates and data-residency details arrive. MCP support I’d count as good news; publishing your tools once as MCP servers lowers the cost of switching platforms later.

Automation Anywhere to acquire Boost.ai

Automation Anywhere · 7 October 2026

Automation Anywhere announced a definitive agreement to acquire Boost.ai, a Norwegian conversational and voice AI company, from Nordic Capital. Closing is expected in the fourth quarter of 2026, subject to customary regulatory approvals; terms were not disclosed. According to the release, the Boost.ai platform supports more than 36 languages and is strongest in regulated sectors such as financial services, telecoms and insurance. The company frames the deal as connecting the customer conversation to the back-office work behind it.

Why it matters. Platform vendors are moving to sell the front end (chat, voice) and the back office (robots, agents) as one package. If you run Automation Anywhere and hold a separate chatbot contract, the renewal conversation will change. The release doesn’t list the supported languages; I wouldn’t plan a consolidation before asking how well Turkish works in production and where the data is processed. One vendor makes integration easier and makes leaving more expensive.

Gartner: procurement leaders are stalling on AI role redesign

Gartner · 8 October 2026

According to the title of Gartner’s 8 October survey release, chief procurement officers are stalling on the role and job redesign that AI requires. Gartner’s page blocks automated access, so this item rests on the release title alone; I couldn’t verify the survey figures on the primary page, so I’ve left them out.

Why it matters. Procure-to-pay is one of the most mature areas for automation. As robots and agents take on the work, the remaining human roles rarely get redefined, and exception queues end up with no owner. If your business case books capacity gains, write on the same page which new role or work that capacity goes to. If you can’t, the gain stays on paper.

---

Next week I’ll be watching how organisations and law firms update their privacy notices after the KVKK decision, and whether UiPath gives a general-availability date for the guardrail and agent review previews.