> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/start-here/ai-agents/secure-and-govern-agent-access/understand-the-podigee-authorization-model.md).

# Understand the Podigee authorization model

Understand how human consent, scopes, account boundaries, permissions, and safety policy combine.

An agent can act only when every authority layer permits the exact operation.

## Authority layers

| Layer               | Question                                                                                                |
| ------------------- | ------------------------------------------------------------------------------------------------------- |
| Human authorization | Did the user connect this client and approve the requested scopes?                                      |
| Service capability  | Does the current Podigee MCP catalog expose this operation?                                             |
| Credential scope    | Does this grant include every required read or write scope?                                             |
| Account boundary    | Does the grant select the account or organization that owns the target?                                 |
| Resource permission | Can this user read or edit the specific podcast, episode, listener, or analytics data?                  |
| Operation policy    | Does the plan, rollout state, allowance, preview, confirmation, and idempotency contract permit it now? |

All layers must allow the action. A visible resource is not automatically editable. A write-enabled server does not add a missing write scope. A broad scope does not cross the selected tenant.

## One grant, one account

Each OAuth grant or MCP personal access token selects one billing account or organization. Another account requires another grant. Partner-wide, employee-wide, and cross-account access are excluded.

## Consequential changes

Preview and confirmation bind the exact action, target, actor, tenant, grant, and request digest. Idempotency binds accepted work to the actor, tenant, operation type, and stable key. Reauthorization requires a fresh preview but does not erase the original operation's provenance.

## Revocation

Revoking a connector grant invalidates its token family. Background operations check current authorization at safe checkpoints and stop when required authority is no longer valid.

## Related tasks

* [Choose permissions and scopes](/documentation/start-here/ai-agents/connect-and-authorize/choose-permissions-and-scopes.md)
* [Review and revoke connected clients](/documentation/start-here/ai-agents/connect-and-authorize/review-and-revoke-connected-clients.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/start-here/ai-agents/secure-and-govern-agent-access/understand-the-podigee-authorization-model.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.