ServiceNowAI & Automation

ServiceNow Arc GA: A UK Rollout Gate for Personal Long-Running Agents

ServiceNow made Arc, its personal long-running enterprise agent, generally available on 21 October 2026 inside EmployeeWorks at no extra cost on Foundation, Advanced and Prime. Here is the rollout gate I would put in front of it in a UK estate before the first laptop gets it.

AQ
Ali Qaiser
AWS Certified | ServiceNow Architect | Enterprise AI Consultant
23 October 2026
9 min read
ServiceNow Arc GA: A UK Rollout Gate for Personal Long-Running Agents
In brief

ServiceNow made Arc, its personal long-running enterprise agent, generally available on 21 October 2026 inside EmployeeWorks at no extra cost on Foundation, Advanced and Prime. Here is the rollout gate I would put in front of it in a UK estate before the first laptop gets it.

Key Takeaways
  • ServiceNow made Arc generally available on 21 October 2026 inside EmployeeWorks.
  • Arc is included at no additional cost with Foundation, Advanced and Prime SKUs.
  • Mac support is live; Windows support is expected within weeks.
  • Arc is governed by the Super Intelligence Control Tower and enforced with NVIDIA OpenShell.
  • Own Arc as a CMDB business service with a named owner and support group.
  • Clean up user roles first, because Arc acts with the employee's permissions.
  • Update the DPIA and privacy notice, and confirm processing location in writing.
  • Prove runtime refusal of out-of-scope actions and rehearse suspending Arc.

What changed

On 21 October 2026, at NVIDIA GTC Berlin, ServiceNow announced the general availability of Arc, which it describes as a personal, long-running AI agent built for the enterprise. The points that matter to anyone running a ServiceNow estate:

  • Arc is generally available now as part of ServiceNow EmployeeWorks, and is included at no additional cost with Foundation, Advanced and Prime SKUs.
  • It is governed and secured by the Super Intelligence Control Tower (the product previously marketed as AI Control Tower) and enforced with NVIDIA OpenShell.
  • Mac support is live; ServiceNow says Windows support is expected within weeks.
  • ServiceNow's recently announced AI Passport (15 October, expected Q4 2026) will be readable by the NVIDIA OpenShell and NVIDIA BlueField DPU enforcement layers, so the same signed credential can decide what Arc, and other agents, may access or execute.

The framing from ServiceNow is "govern once" in the Control Tower and have both software and silicon honour that decision. That is a sensible architecture. It is also a reason to be disciplined, because "no additional cost" and "long-running" together mean Arc can spread across a workforce very quickly.

Why a personal agent is a different risk shape

Most agent work we have done on ServiceNow so far has been workflow agents: an agent attached to a case type, an incident queue or a catalogue item, with a clear owner and a clear table. Arc is different in three ways.

  1. The principal is a person, not a process. Arc acts for an individual employee. Its effective permissions are bounded by what that employee can do, plus whatever tools it has been granted. Over-privileged users become over-privileged agents.
  2. It runs for a long time. A long-running agent holds context and keeps working while the employee does something else. That is the value, and it is also why you need runtime checks rather than a one-off approval at the start.
  3. It sits on the endpoint. Mac today, Windows soon. That brings endpoint management, device posture and local data into scope in a way a purely server-side agent does not.

None of that is a reason not to use it. It is a reason to roll it out the way you would roll out any new privileged client: in rings, with evidence.

The UK rollout gate

This is the gate I would agree with the CAB and the DPO before Arc reaches general staff.

1. Decide who owns Arc as a service

Create Arc as a business service and application service in the CMDB, with a named service owner, a support group and an assignment path. If an Arc action goes wrong at 4pm on a Friday, the Service Desk needs to know who picks it up. Link it to EmployeeWorks and to the Super Intelligence Control Tower so dependency views make sense.

2. Clean up the humans before the agents

Because Arc acts as the employee, review roles and group membership for your first rings. In most instances I look at there are users carrying admin-adjacent roles from a project two years ago. Remove them first. A quick aggregate of role assignments per user, filtered to the pilot group, usually finds the outliers in minutes.

3. Write the tool and data scope down

List which tools, MCP servers and record types Arc is allowed to use in each ring. Keep it specific: "read incidents assigned to my groups" is a scope; "ITSM access" is not. Store that list alongside the Control Tower configuration and treat any widening as a new change, not a tweak.

When AI Passport lands, these scopes become the content of the passport. Writing them now means you are ready to issue passports rather than starting the exercise in Q4.

4. Do the UK GDPR work up front

A personal agent will see personal data: emails, HR cases, customer records. Before ring one:

  • Update or complete the DPIA for EmployeeWorks to cover Arc explicitly, including what it can read, what it retains and for how long.
  • Confirm with your ServiceNow account team where Arc processing and any model inference take place, and get it in writing. Do not assume; check the current data residency documentation for your instance and contract.
  • Update the employee privacy notice so staff know an agent may act on their behalf and what is logged.
  • Agree how a subject access request would surface Arc activity logs.

5. Prove the deny path

For every ring, test that Arc is refused when it tries to go outside scope: a record it should not read, a tool it was not granted, an action needing approval. Capture the evidence (screenshots or logs) in the change record. A prompt that says "don't do X" is not a control. A runtime refusal is.

6. Endpoint readiness

With Mac live and Windows coming, bring the endpoint team in now. Confirm how Arc is deployed and updated through your device management tooling, which device posture you require, and how you remove it quickly from a lost or compromised device. Plan the Windows ring as a separate change when support arrives; do not let it ride on the Mac approval.

7. Rehearse the stop button

Decide who can suspend Arc for one user, one group, or everyone, and rehearse it. Time it. If you cannot stop a long-running agent within minutes, it is not ready for a regulated function.

Suggested rings

  • Ring 0 (two weeks): the platform team and a handful of IT staff on Mac, read-mostly tools, daily review of Control Tower activity.
  • Ring 1 (four weeks): one business function with low personal-data exposure, write actions limited to the user's own records.
  • Ring 2: wider rollout, Windows once supported and separately approved, AI Passport enforcement switched on when it becomes available to you.

For financial services teams, ServiceNow's Operational Resilience solution (announced as available on 22 October) is worth looking at alongside this, because it puts AI discovery, third-party risk and business continuity on the same record. If Arc is going near important business services, map it to them for your operational resilience self-assessment.

What to measure

  • Arc actions per user per day, and the share that needed approval.
  • Out-of-scope attempts refused at runtime (this should be non-zero in testing and low in production).
  • Incidents and requests where Arc was involved, tagged so you can report on them.
  • Time to suspend in your rehearsal.
  • Hours saved, measured honestly against a baseline, not a vendor estimate.

Bottom line

Arc being included at no extra cost removes the usual commercial brake, so the brake has to be operational. Treat it as a privileged client, own it as a service, clean up roles first, write scopes you can turn into AI Passports later, do the DPIA properly, and prove the agent gets refused when it steps outside its lane. Do that and Arc can go wide quickly without becoming the next shadow AI problem.

Expert Commentary

Arc changes the principal from a process to a person. That is the single most important thing to understand: an over-privileged employee becomes an over-privileged agent that keeps working while they are in a meeting. Clean up roles first, write scopes you can turn into AI Passports, and prove the deny path before ring one.

Topics
ServiceNowArcEmployeeWorksSuper Intelligence Control TowerAI PassportNVIDIA OpenShellAI AgentsUK GDPRCABUK
All insights

Need Help With Your Implementation?

Arrange a consultation about ServiceNow, AI agent automation or AWS.

Schedule a Consultation