Canon term · Authority

Consent Grant

A permission issued by a principal to a named third party to access specified data, for a specified purpose, for a specified duration, revocable at any time by the principal and enforced at the interface.

  • StatusIndustry term
  • AdoptionWidely used
  • LayerGovernance

Why it matters

The most useful precedent in agentic governance, and almost nobody in the field cites it. Scoped, time-bounded, revocable, granted to a named party and enforced at the API — open banking has been running bounded delegated authority at national scale for years while agent governance treats the problem as unprecedented. It is not unprecedented. It is solved for data access, and the pattern transfers to action with one change: the object of the grant.

Where it comes from

Open banking. Formalized in the FDX API standard in North America and in equivalent open banking regimes elsewhere.

Defining sources

What it is not

These are routinely confused with Consent Grant. The distinctions have consequences for how a system is governed.

  • Authority Grant

    Consent governs what a party may SEE. An authority grant governs what it may COMMIT. Everything else about the two structures is close enough to borrow from.

  • Terms of Service

    Consent is specific, scoped and revocable per relationship. Terms of service are blanket and non-negotiable.

How it connects

What it needs

  • Consent Grant depends on FDX Standard

What relies on it

MARQUE questions it addresses

  • AuthorityWhat is the agent permitted to commit, and who granted that?

Connected through the MARQUE (a reference framework organized around eight questions) crosswalk, an editorial mapping. These objectives from the Financial Services AI Risk Management Framework are assigned to the same questions that this term addresses. The ones sharing most of this term's vocabulary are shown first, as a reading aid. The assignment is to the question, not to the term: the source does not map this term to any objective directly.

Question: Authority · 39 control objectives assigned

  • GV-2.1.1AI Risk Management Roles and ResponsibilitiesGovern
  • MS-2.1.3Centralized TEVV Repository and AccessMeasure
  • MS-2.10.1Initial Privacy Risk AssessmentMeasure
All 39 objectives assigned to Authority

Cite and reuse

Cite the identifier QIS-TERM-00024, not the URL: identifiers are stable, URLs may change. This entry is free to read, quote and index under the dual license. Corrections sent to editor@qisfund.com are published.

Technical details: identifier, graph relationships and record
QIS-TERM-00024: outbound relationships as published in api/graph.json and api/lexicon.json
PredicateTarget identifierTargetPredicate meaning
relatedToterm:authority-grantAuthority GrantAn association too weak or too general for a stronger verb.
addressesmarque:authorityAuthorityThe subject speaks to the object as a question or concern.
dependsOnstd:fdxFDXThe subject cannot function correctly without the object.
constrainsterm:agent-identityAgent IdentityThe subject bounds what the object may do.
relatedToterm:authorityAuthorityAn association too weak or too general for a stronger verb.
Canonical identifier
QIS-TERM-00024
Tier
Canonical industry term
Domain · layer
Authority · Governance
Semantic aliases
None recorded
First published
2026-08-02
Last reviewed
2026-08-02 · 180-day cycle