> 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/mcp-reference/account-and-tenant-binding.md). # Account and tenant binding One-account grant binding, organization selection, actor identity, and cross-account exclusion. One connector grant or MCP personal access token selects exactly one billing account or organization. ## Tenant identifiers * Account grant: `account:`. * Organization grant: `organization:`. The tenant identifier is opaque to client authorization logic. Use it to verify that subsequent requests stay in the intended account. ## Bound identities Every grant records the human actor, account owner, optional organization, client or token identity, resource, scopes, consent, contract version, expiry, and revocation state. Podcast and episode queries are limited to resources inside the selected tenant. Resource-level permissions apply within that boundary. ## Excluded access Partner-wide, employee-wide, external collaboration, and cross-account aggregation are not included in one grant. Another account requires another authorization and grant. ## Durable provenance Operations and audit events snapshot the originating user, tenant, credential type, scopes, and contract versions. Reauthorization can supply current execution authority for the same actor and tenant, but it does not replace the recorded origin. ## Account mismatch An ID from another tenant is not visible through the current grant. Reconnect to the correct account instead of guessing or probing IDs. --- # 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/mcp-reference/account-and-tenant-binding.md?ask=&goal= ``` `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.