The Factory Floor’s Newest Worker Runs on a Model

A new engineer on a production line does not get access to every design file on day one. They get access scoped to their project, oversight from a lead engineer, and a record of what they touched. Most manufacturers deploying AI agents against PLM and file-sharing systems skip all three. The agent gets connected, given broad access to move fast, and left to operate with far less oversight than the newest, least trusted engineer would ever receive.

That gap is not a minor oversight. An AI agent that can read design files, send communications or move data on a manufacturer’s behalf is, functionally, an actor with access to proprietary systems, exactly like an engineer. This article looks at why AI agents in manufacturing routinely get less governance than a human would, and what applying the same standard actually requires.

Executive Summary

Manufacturers that would never give a new engineer unrestricted access to every design file routinely give exactly that to AI agents, because agent deployment is treated as a technical integration problem rather than a governance one. The result is systems that can read, move and send proprietary data with fewer checks than the people who built them. For engineering and IT leaders, the practical question is simple: would this level of access be acceptable if the actor were a person, and if not, why is it acceptable for an agent.

Key Takeaways

1. AI agents in manufacturing are often deployed with broader access to design data than any new hire would receive. Speed of adoption has outpaced the basic governance hygiene manufacturers already apply to people.
2. An agent should inherit the permissions of the person authorising it, not a separate standing credential. A broad service account for an AI agent recreates exactly the over-privileged access manufacturers spent years eliminating for humans.
3. Sensitive actions, sharing designs with suppliers, need an approval step regardless of who, or what, initiates them.
4. Every AI action needs to be attributed to a specific person and logged with the same rigour as human activity. An audit trail that treats “the AI did it” as sufficient attribution is not an audit trail.
5. Governance built for AI agents from the outset does not require new infrastructure. The access control, approval and logging model manufacturers already use for staff extends directly to agents.

Why AI Agents Get Onboarded With Less Scrutiny Than Humans

The gap is rarely intentional. It is a byproduct of how quickly agent capabilities have moved from experimental to operational, and how differently technical teams and security teams tend to think about the problem.

Speed of Adoption Outpaces Governance by Design

Connecting an AI agent to a PLM system is often a configuration task measured in minutes: grant an API key, authorise a scope, done. The equivalent governance a new engineer goes through, defined roles, a documented access review, was built around people joining at a human pace.

“It’s Just a Tool” Thinking Understates What an Agent Can Do

Because an AI agent is described as a tool rather than a user, it is easy to reason about it the way manufacturers reason about software rather than the way they reason about people with access to design data. A tool that can autonomously read a design file, decide to forward it, or act on instructions embedded in content it processes is exercising judgement in a way a spreadsheet does not.

What “Same Governance as Humans” Actually Requires

Extending human-grade governance to AI agents is not a new discipline. It is the same three components manufacturers already apply to people, applied consistently to agents as well.

Identity Inheritance Instead of Standing Privilege

The single most important design choice is whether an agent operates under its own broad, persistent credential or inherits the specific permissions of the person who authorised it. A standing service account with wide access to design files recreates precisely the over-privileged account security teams have spent years trying to eliminate. An agent that can only do what the authenticating user could already do is bounded the same way a human colleague acting on someone’s behalf would be.

Approval Gates Before Consequential Actions

An engineer sharing a design with a supplier typically encounters a confirmation step before it happens. An AI agent attempting the same class of action should hit the same kind of gate.

Attribution and Audit, Not Just Activity Logs

Human-grade audit trails attribute every action to a specific accountable person. An AI agent’s actions need the same standard: not “an automated process did this” but which user authorised the agent, and what it actually did.

Where the Gap Shows Up in Practice for Manufacturers

The most common pattern is a single, broadly scoped credential issued once and left in place indefinitely, alongside agents configured to share designs with suppliers without any confirmation step, because building that pause takes more engineering effort than letting the agent proceed. Even where activity is logged, the log often cannot answer which specific person is accountable for a given action.

Building Agent Governance on the Access Model You Already Have

The practical path forward is not a new governance framework built specifically for AI. It is applying the identity, approval and audit model a manufacturer already runs for its staff, consistently, to its agents.

How a Data Control Plane Applies Human-Grade Governance to AI Agents

The Kiteworks Data Control Plane connects AI agents through a secure interface built on OAuth 2.0 authentication, where every agent operation inherits the authenticated user’s existing permissions rather than a separate standing credential, and dynamic attribute-based policies evaluate agent requests exactly as they would a human request. Sensitive actions, including membership changes and outbound sends, require explicit confirmation before proceeding, and administrators can globally disable destructive tools. Every agent operation is captured in a tamper-proof, unthrottled audit log, attributed to the authorising user and fed directly into SIEM tooling, so an agent’s activity is exactly as accountable as an engineer’s would be.

Manufacturers that want to see whether their current AI agent deployments would pass the same access review a new hire goes through can schedule a custom demo to walk through how identity-scoped, audited agent governance applies to their own environment.