Should AI agents get their own company identity and credentials?

Alongside the personal, user-trained dot, OpenAI's announcement describes a second category: "specialist dots with their own identity for access management, IT-provisioned hardware, and support for deep integrations with a company's systems of record." OpenAI frames these as built "to take on well-defined responsibilities inside organizations" rather than to assist one person. The announcement is explicit that "your company sets up each dot with its own identity, credentials, and access to the systems it needs to complete its tasks" — identity and access are provisioned by the organization, not accumulated informally through use the way a personal dot learns a user's preferences.

OpenAI ties this to concrete back-office functions, saying it is "building on lessons from early testing inside OpenAI across procurement, invoice processing, email marketing, customer support, and commercial contracting." As it works, OpenAI says the specialist dot "adapts to new information and improves with feedback from your team" — the same learning-from-feedback mechanism described for personal dots, but pointed at a team rather than an individual, and bounded by the specific systems and credentials the company has provisioned rather than by whatever the dot happens to have access to.

This is the same structural move as How does Google separate temporary agents from persistent ones?: both vendors found it necessary to give a persistent agent its own organizational identity — a company email and role for Google's coworker agents, "its own identity, credentials, and access" for OpenAI's specialist dots — once the agent is meant to hold a defined responsibility rather than execute a one-off task. It also extends Can a protocol split agent access from agent incentives?: Sierra's protocol lets a company set what any agent may do across channels, and OpenAI's specialist-dot identity provisioning is one concrete instance of a company doing exactly that internally. Read against Does labeling AI as an employee change how managers oversee it?, giving a dot its own company identity is close to the "org chart already lists AI agents" condition that study found most strongly associated with reduced human oversight — which makes OpenAI's auto-review and Custom Rules, described in Can read-only tools and approval rules prevent autonomous agent failures?, load-bearing rather than optional for this configuration.

OpenAI calls this a "preview" and names only five internal functions it has tested against, all inside OpenAI itself — the announcement gives no customer deployment data, no description of how access is revoked or audited once granted, and no account of what happens when a specialist dot's provisioned access turns out to be wrong for a task. The claim established here is only that OpenAI has decided persistent organizational identity is the right abstraction for giving an agent a defined role in a company, not that this particular credentialing model resists misuse or scales past the back-office functions it has tried internally.