Agent Authority
Home/Guides/Foundations

Corporate Authority for Agents

Foundations · Guide 3Last reviewed: November 2026About 14 minutes

Summary

  • In a corporation, an agent’s authority ordinarily traces back to the board, which manages the business unless the statute or the charter provides otherwise. The board delegates to officers, officers delegate through the company’s delegation of authority policy, and someone in that chain deploys the agent. In an LLC or partnership, the operating or partnership agreement usually sets the chain instead, and statute fills the gaps. In a Delaware LLC, unless the LLC agreement provides otherwise, the members manage the company and each member or manager can bind it. In a general partnership under the uniform partnership act, a partner’s act that apparently carries on the business in the ordinary way binds the partnership, despite an internal restriction, unless the other side knew or had received notification that the partner lacked authority; Delaware’s statute uses a broader notice standard that also covers reason to know.1
  • Both Delaware and the Model Business Corporation Act require directors to be natural persons, and neither statute’s officer provisions provide for software to hold authority in its own right. An agent acts under the authority of whoever in the company’s chain of delegation approved its deployment and limits, not necessarily of the engineer who sets it up.
  • Many delegation of authority policies were written for people and say nothing about AI agents. That silence leaves open whether anyone with enough authority approved what the agent does.
  • A short board resolution and one added paragraph in the policy close most of the gap. The board materials behind them are among the records stockholders can inspect.

Where an agent’s authority starts

Guide 1 and Guide 2 start from the agent’s mandate. The mandate itself has to come from somewhere.

  1. StatuteThe business is managed by or under the direction of the boardLegislature
  2. Charter and bylawsOfficer titles, duties and any limits on the boardStockholders and board
  3. Board resolutionsWhat officers may approve, and whether they may use automated systems to actBoard
  4. Delegation of authority policySpending and signing limits by role, and who may deploy agentsCFO, general counsel
  5. Agent mandateThe approver, the task and the limits for one agentBusiness owner
  6. CredentialsWhat the systems let the agent doEngineering

The highlighted layers are where agent deployments usually break the chain. Each layer must fit inside the one above it.

Boards, officers and delegation

Under Delaware law, a corporation’s business is managed by or under the direction of its board.2 Officers hold the titles and duties the bylaws or board resolutions give them.3 The Model Business Corporation Act, followed in many states, takes the same approach.4 Boards delegate most operating decisions to officers, and officers delegate further through internal policies. That is normal and lawful.

Two limits matter here. The board directs the business; it can delegate management but can’t give up oversight of it. Some decisions can’t be delegated even to a board committee, such as matters that need stockholder approval.5 No agent should be approving those. The sample board resolution below says so, and a mandate should never include them among the agent’s permitted actions.

Nothing in these statutes contemplates software holding authority in its own right. So the working answer, consistent with the tool view, is that an agent exercises the authority of the officer or employee who approved its deployment and limits. That approver’s own authority is the ceiling. The approver isn’t necessarily the person who sets the agent up: an engineer who configures an agent on the instructions of the head of procurement is carrying out that manager’s decision, and the agent’s authority is the manager’s to give, within the authority the board or the delegation policy has given them, not the engineer’s. An individual director, by contrast, has no power to authorize a deployment just by holding that seat; the board acts as a body. This is a working answer for Delaware and Model Act corporations; LLCs and other entities follow their own statutes and operating agreements.

The delegation of authority gap

Most companies have a delegation of authority policy: a table of who may approve what, by amount and type. It was written for people, and it usually leaves three questions unanswered.

  • May an approver act through an agent at all? A policy that lets a director approve purchase orders up to $25,000 assumes she reviews each one. An agent placing orders under her name without review may not be what the policy allows.
  • Who may approve a deployment? Setting up an agent that will make hundreds of commitments is a bigger decision than approving any one of them. Many policies don’t say who makes it.
  • Whose limit applies? The agent’s spending limit is usually set by the business owner, and the limit built into its credentials by engineering. If the credentials allow more than the business owner’s limit, the systems will accept orders nobody approved. The policy should say that the business owner’s limit governs and name who checks that the credentials match it.

Silence doesn’t usually help the company against outsiders. Under apparent authority and the tool view, a vendor that saw a working corporate account can often hold the company to the order. The gap matters internally: for controls, for audits, and for who answers for the loss.

You can’t delegate more than you have

Agency law’s rule for subagents points the same way. An agent can appoint a subagent only if it has authority to do so, and the appointing agent stays responsible to the principal for what the subagent does.6 Whether or not an AI agent is an agent in law, the principle is a sound design rule: an agent’s limits must fit inside the limits of the person who approved it.

A manager whose own approval limit is $5,000 can’t give an agent a $10,000 cap and call orders between the two authorized. Internally, those orders were never approved by anyone with authority to approve them. Externally, the company may still be bound, which is the worst combination: exposure without approval.

Oversight duties

Delaware directors must make a good-faith effort to put in place a system for monitoring and reporting on the company’s central compliance risks, and must respond to red flags.7 The Delaware Supreme Court has stressed that this applies with special force to risks that are “mission critical” for the business.8 The Court of Chancery has held that officers owe a similar duty within their areas of responsibility.9

We haven’t found a decision applying these cases to AI agents, as of November 2026. But for a company whose agents buy, pay, price or make promises at scale, agent activity can become a central risk. The practical response is modest: a register of agents that can commit the company, a named officer responsible for them, and periodic reports to the board or a committee.

For the board: the question to ask management is not “do we use AI?” but “which systems can commit the company, under whose authority, and how would we know if one went wrong?”

Follow-up questions for a periodic report:

  • What is the most any single agent, and all agents together, can commit the company to in a month?
  • Which of those limits are enforced by systems, and which exist only in policy?
  • Can any agent both commit the company and make payments, beyond paying for its own orders with a capped company card, or change where payments go?
  • How quickly can each agent be shut off, and when was that last tested?
  • Can we show what authority each agent held on any past date?
  • Has any agent acted outside its authority since the last report, and what happened?

Board records

Since 2025, Delaware’s inspection statute lists the “books and records” a stockholder can demand. The list includes board and committee minutes and the materials given to the board or a committee in connection with actions it took. A stockholder still needs a proper purpose to inspect them, and its demand must be made in good faith, describe the purpose and the records sought with reasonable particularity, and seek records specifically related to that purpose.10 If the corporation doesn’t have certain listed records, such as board minutes, the court can order their functional equivalent, to the extent necessary and essential to the stockholder’s purpose.11 Whether an email can stand in for a missing record depends on what it says and how it was used, not on its form. Beyond that, a court can order other records, such as emails, only if the stockholder shows a compelling need and proves by clear and convincing evidence that they’re necessary and essential to that purpose.12

Two consequences follow. A board resolution approving agent deployments, and the materials presented with it, are core inspectable records. Write them as if a stockholder will read them. Agent logs are ordinarily outside the list, but they may still be reached in litigation discovery, so keep them with that in mind.

Worked example

Acme’s delegation of authority policy lets its Director of IT Procurement approve orders up to $25,000 and lets managers approve up to $5,000. A procurement manager sets up an agent with a $10,000 per-order cap. It places an $8,000 order.

  • Is the order binding on Acme? Probably. The vendor saw Acme’s account and card, and had no notice of any internal limit.
  • Was it authorized internally? No. The manager could approve only $5,000, and the agent can’t have more authority than the person who approved its deployment, which here was the manager herself.
  • Who answers for it? Internally, the manager exceeded her authority. But the policy never said whether managers may deploy agents or how agent caps relate to personal limits, so the failure is also the policy’s.
  • The fix. The policy should say that agent caps can’t exceed the approver’s own limit, and that deploying an agent above a set threshold needs approval one level up. With that rule, the Director would have approved the deployment and the $10,000 cap would sit inside her $25,000 limit. If the agent also pays with a company card, the sample policy language below requires a second approval, such as the CFO’s, as in the Agent Mandate example.

Sample board resolution

This resolution is for a company whose agents can commit it to contracts or payments. The officers, thresholds and reporting should be adapted to the company.

Sample language

WHEREAS, the Corporation uses or intends to use software systems, including artificial intelligence agents, that can take actions on its behalf, such as placing orders, accepting terms, making payments and communicating with third parties (“Automated Agents”); and WHEREAS, the Board wishes to confirm the authority under which Automated Agents act and to provide for oversight of their use; NOW, THEREFORE, BE IT RESOLVED, that each officer and employee of the Corporation who is authorized under the Corporation’s Delegation of Authority Policy (the “Policy”) to approve a type of transaction may cause that type of transaction to be carried out by an Automated Agent, provided that (a) the Automated Agent’s limits do not exceed that person’s own authority under the Policy, (b) the deployment is documented in a written mandate that identifies the approver, the Automated Agent, its permitted actions and its limits, and (c) the deployment complies with the Policy’s requirements for Automated Agents; RESOLVED FURTHER, that no Automated Agent may take any action that requires approval of the Board, a committee of the Board or the stockholders; RESOLVED FURTHER, that the [Chief Financial Officer] is designated as the officer responsible for maintaining a register of Automated Agents that can commit the Corporation to contracts or payments, and shall report to the [Audit Committee] at least [twice a year] on their use, limits, incidents and controls; and RESOLVED FURTHER, that the officers of the Corporation are authorized to amend the Policy consistent with these resolutions.

Keep it short. The resolution sets the principle and names who is responsible. Thresholds and procedures belong in the delegation of authority policy, where they can change without a board meeting.

Sample policy language

This paragraph is for the company’s delegation of authority policy.

Sample language

Automated Agents. An Automated Agent may carry out a type of transaction only under a written mandate approved by a person authorized under this Policy to approve that type of transaction. An Automated Agent’s per-transaction and aggregate limits may not exceed the approving person’s own limits. Any deployment whose aggregate limit exceeds $[amount] per [month], or that permits payments, signatures or acceptance of nonstandard terms, also requires approval by [the approving person’s manager / the CFO]. Each mandate must be recorded in the Automated Agent register before the agent is given credentials. If the approving person leaves, changes roles or has their delegated authority reduced, the Corporation must pause the Automated Agent until someone with the required authority approves its mandate again.

Note the last sentence. When the person who approved an agent leaves or changes roles, review where the agent’s authority comes from and how long it lasts. A grant from the company doesn’t lapse just because the approver leaves; the Agent Transaction Addendum says so expressly for counterparties (section 17(d)). The internal pause gives the company time to verify the delegation and name a responsible approver. If the company also wants to suspend the agent under the Addendum, it must give the agreed notice.

For agents that buy goods and services, the toolkit’s Autonomous Procurement Policy is a fuller version, with authority levels, vendor rules, enforced limits, and human approval.

Checklist

  1. Existing board and officer delegations cover acting through agents. Where they are unclear or insufficient, the board has confirmed by resolution that officers and employees may act through agents within their own authority.
  2. The delegation of authority policy covers agents, including who may approve a deployment.
  3. Every agent’s limits fit inside its approver’s limits.
  4. A register lists each agent that can commit the company, its approver and its mandate. The Agent Registry is a template, with each entry pointing to the agent’s signed Agent Mandate.
  5. A named officer is responsible, and the board or a committee receives regular reports.
  6. An approver’s departure, role change or reduction in delegated authority triggers a pause and reapproval.
  7. Board materials about agents are written with stockholder inspection in mind.

Both sides of the deal

If you deploy agents

  • Adopt the resolution and policy language before agents can commit the company at scale.
  • Tie each mandate to a named approver whose limit covers it.
  • Re-approve mandates when people change roles.

If you build agents

  • Let customers record each agent’s approver and mandate in the product, and keep earlier versions of those records.
  • Support per-agent limits that customers can match to their own policies.
  • Expect enterprise buyers to ask how your product fits their delegation of authority policy.

Open questions

  • Could a board delegate authority directly to a software system, rather than to a person who deploys it?
  • Do a company’s bylaws or delegation policy permit authority to be exercised through software at all, or do they need amending first?
  • May an officer who holds delegated authority pass it on to an agent, or is that a further delegation the officer’s grant doesn’t allow?
  • Will courts treat a company’s failure to monitor agents that commit it at scale as an oversight failure?
  • When the person who approved an agent leaves, does the agent’s authority end, continue, or pass to the successor?
  • Will agent logs become part of the corporate records stockholders can inspect as agents take on more of the company’s business?
Sources
  1. Del. Code Ann. tit. 6, § 18-402 (opens in a new tab); Unif. P’ship Act § 301(1) (opens in a new tab) (1997) (amended 2013); Del. Code Ann. tit. 6, § 15-301(1) (opens in a new tab); § 15-102(b) (opens in a new tab) (notice). ↩
  2. Del. Code Ann. tit. 8, § 141(a)–(b) (opens in a new tab) (board management and natural-person directors). ↩
  3. Id. (opens in a new tab) § 142(a). ↩
  4. Model Bus. Corp. Act §§ 1.40, 8.01(b), 8.03(a), 8.41 (opens in a new tab) (Am. Bar Ass’n 2025 rev.). ↩
  5. Del. Code Ann. tit. 8, § 141(c)(1)–(2) (opens in a new tab). ↩
  6. Restatement (Third) of Agency § 3.15 (opens in a new tab) (Am. L. Inst. 2006). ↩
  7. In re Caremark Int’l Inc. Derivative Litig. (opens in a new tab), 698 A.2d 959 (Del. Ch. 1996); Stone v. Ritter (opens in a new tab), 911 A.2d 362 (Del. 2006). ↩
  8. Marchand v. Barnhill (opens in a new tab), 212 A.3d 805 (Del. 2019). ↩
  9. In re McDonald’s Corp. S’holder Derivative Litig. (opens in a new tab), 289 A.3d 343 (Del. Ch. 2023). ↩
  10. Del. Code Ann. tit. 8, § 220(a)(1)(e)–(f), (b)(2) (opens in a new tab), as amended by S. Sub. 1 for S.B. 21, 85 Del. Laws ch. 6 (2025) (opens in a new tab) (applies to demands made after Feb. 17, 2025). ↩
  11. Del. Code Ann. tit. 8, § 220(f) (opens in a new tab). ↩
  12. Del. Code Ann. tit. 8, § 220(g) (opens in a new tab), as amended by S. Sub. 1 for S.B. 21, 85 Del. Laws ch. 6 (2025) (opens in a new tab). ↩

Sample language is illustrative and must be adapted to the company, its governing documents and its state of incorporation.