Authority is the recognised power to decide, direct, approve, permit, enforce or represent within a defined scope.
Authority can come from law, office, ownership, delegation, expertise, contract, community recognition or emergency conditions. It is never complete without a boundary: who may act, over what, where, for how long, and under which higher rules?
Quick answer: how should authority be categorised?
- Source: law, office, ownership, delegation, contract, expertise or custom?
- Scope: what decisions, resources or people fall under it?
- Jurisdiction: where does the authority apply?
- Delegation: can it be passed onward?
- Duration: standing, temporary, acting, emergency or event-bound?
- Legitimacy: why should others recognise it?
- Evidence: what proves the authority exists?
- Review: who can challenge or oversee it?
- Revocation: who can remove or narrow it?
- Conflict: what happens when authorities disagree?
This article complements How to Categorise Roles and How to Categorise Permissions. Roles can carry authority; permissions operationalise particular actions that authority allows.
Authority is not power
Power is the ability to influence outcomes. Authority is power recognised as legitimate within a rule system, institution or relationship.
Authority is not expertise
An expert may know more than the decision-maker without holding formal authority. Expertise can justify influence without creating jurisdiction.
Authority is not ownership
Owners often have authority over assets, but legal, contractual and regulatory limits can constrain what ownership permits.
Legal authority derives from law
Statutes, constitutions, regulations and court orders can create formal authority under a jurisdiction.
Organisational authority derives from office
Boards, managers, principals and supervisors can hold authority because of formally assigned roles.
Delegated authority comes from another authority
Delegation should preserve source, scope, duration and whether onward delegation is allowed.
Contractual authority comes from agreement
Agents, service providers and signatories may act because a contract grants specific decision rights.
Expert authority is epistemic rather than coercive
Professional credibility can justify deference on factual questions while leaving final governance authority elsewhere.
Customary authority can emerge socially
Communities may recognise leadership or decision rights through convention even without formal documents.
Emergency authority needs strong boundaries
Temporary powers granted during crises should define trigger, scope, expiry, review and non-waivable protections.
Scope should be action-specific
Authority to approve expenditure does not imply authority to alter curriculum, delete records or disclose private information.
Jurisdiction should be explicit
Authority may be valid only within one organisation, country, project, site or system boundary.
Standing authority persists
Permanent roles can hold continuing authority until revoked or superseded.
Temporary authority needs expiry
Acting appointments, emergency delegations and project powers should end automatically or trigger review.
Authority can be exclusive or shared
Some decisions belong to one role; others require joint approval or distributed consent.
Concurrent authority creates coordination needs
Two authorities may govern different dimensions of the same object, such as safety and finance. Their precedence rules should be known before conflict occurs.
Higher authority can constrain lower authority
Local rules, organisational policies and delegated permissions may remain subordinate to law, rights, contracts or superior governance.
Legitimacy and legality are related but distinct
An authority can be legally valid yet socially contested, or socially accepted while lacking formal legal power. Classification should preserve both dimensions where relevant.
Authority evidence should be inspectable
Appointment letters, statutes, contracts, board resolutions, credentials and delegated mandates provide different kinds of proof.
Review preserves accountability
Appeal, audit, board oversight, judicial review and supervisory review create return paths when authority is misused or disputed.
Revocation should be as explicit as grant
An authority that can be granted but not reliably withdrawn can create lasting governance risk.
Authority drift should be monitored
Informal practice can gradually expand beyond the original mandate. Periodic review should compare actual decisions with authorised scope.
Conflicting authority needs precedence rules
When authorities disagree, resolve conflict through jurisdiction, hierarchy, narrower scope, specific mandate, timing or another governed rule rather than personality.
AI agents should not infer authority from capability
Being technically able to publish, delete or purchase does not mean the system is authorised to do so. Capability and authority are separate classifications.
A practical authority record
- authority ID;
- holder;
- source;
- actions authorised;
- resources or subjects governed;
- scope and jurisdiction;
- delegation rights;
- higher authority;
- evidence of grant;
- start and expiry;
- review route;
- revocation authority;
- conflicts and precedence;
- version.
The deeper idea
Authority is permission backed by recognised legitimacy and scope. Its quality depends on how clearly its source, boundary and accountability path are defined.
To categorise authority well is to know where the power comes from, exactly what it covers, how it can be delegated, who can review it, and when it ends.
Final answer
Categorise authority by source, scope, jurisdiction, delegation, duration, legitimacy, evidence, review, revocation and conflict. Keep authority separate from expertise, ownership and raw power, and make boundaries and accountability explicit before consequential decisions are made.