Skip to content

Stockertim Dictionary · Artificial intelligence · Cybersecurity

Permission scope

Also called OAuth scope, access scope, permission scopes

In short

A permission scope is a named slice of access granted to an application or connector, such as reading orders or creating draft bills, so it receives only the rights its task needs.

  • Intermediate
  • Concept
  • Checked

In detail

Rather than handing an application a full password, modern systems grant it a token limited to particular scopes. Each scope is a named permission such as "read calendar", "send email" or "create draft bill". When a connector or AI tool is set up, it asks for the scopes it wants, the person signing in sees the list and approves it, and the system then refuses anything outside those scopes. The OAuth 2.0 authorisation framework, widely used for this sign-in step, defines scope as part of the access request.

How finely scopes are drawn depends on the provider. Some offer precise ones that separate reading from writing and drafts from sending; others offer a single broad scope such as full mailbox access. Where scopes are coarse, teams narrow access another way, for example with a dedicated account that can see only one folder.

Scopes are the practical form of least privilege for connected AI. An assistant that only needs to read invoices should not hold a scope that also lets it pay them, because if it is misled by injected instructions or simply makes an error, the scope sets the ceiling on the damage.

Scopes drift. Connectors often request more than their current use needs, approvals are clicked through, and old grants stay active after a workflow is retired. Periodic reviews of granted scopes catch this.

Worked example

An AI assistant at Thornbury Builders Merchants is connected to the accounts package to answer supplier queries.

  1. The connector asks for four scopes: read invoices, read payments, create bills and approve payments.
  2. The task only needs the first two, so the request is narrowed to read invoices and read payments.
  3. Six months later a scope review finds an old grant with approve payments from a retired workflow and revokes it.

The assistant can answer queries but cannot create bills or approve payments, whatever it is asked.

In practice

Security and IT teams list the scopes each connector holds, approve only those the task needs, prefer read-only scopes at first, and review and revoke grants on a schedule and whenever a workflow is retired.

Watch out

  • Approving a connector's default request often grants far more than the task needs.
  • Removing a workflow does not always revoke the access it was granted.

Learn it properly

Official sources

Facts last checked on 9 November 2026.

Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.

English