Organizational authority

In Simon’s organizational account, authority is a relationship in which one person’s decision guides another’s action. Its exercise depends on behavior and acceptance, not merely a title or a formal organization chart. A communicated decision can become a premise for the recipient’s choice without the recipient independently deciding its merits on that occasion. (Chapter VII, printed pp. 178–180)¹

Uses and boundaries

Simon initially distinguishes authority from persuasion and suggestion: the latter work through the recipient’s assessment of reasons. He then broadens his usage to include suggestions accepted without critical review, including reliance on expertise. The same pair of people can act through authority on one occasion and through persuasion on another. These qualifications matter when applying his definition. (Chapter VII, printed pp. 179–181)¹

This descriptive account does not establish moral legitimacy, legal authority, or a software permission. An agent’s tool access is not evidence that a user authorized a particular action. Authority concerns the acceptance of Decision premises; Common ground concerns shared conversational assumptions and is not an authorization mechanism.

Operational example

An illustrative assistant may accept a user’s approved spending ceiling as a governing premise while treating a vendor’s recommendation as evidence to evaluate. Record who supplied each instruction and its scope. This is an application to software delegation, not a claim that Simon’s analysis of human organizations directly specifies an access-control system.

Footnotes

1. Simon, Herbert A. Administrative Behavior: A Study of Decision-Making Processes in Administrative Organizations. Fourth edition. The Free Press, 1997. ISBN 9780684835822. Publisher edition. Inspected Chapter VII, printed pp. 178–181 (PDF pp. 98–99). The private scan uses two-page spreads. ↩ ↩²