App Permissions and Grants
Most marketplace apps only ever touch their own sandbox. Some go further: an app published by a logistics partner might receive your new orders as events, or an app might need to write fulfilments back to your connected Shopify integration. Every one of those capabilities is modelled as a grant — a permission row naming a single tool the app may call — and your organisation controls each grant individually.
Where grants come from
Section titled “Where grants come from”Grants are created automatically when you install an app whose manifest declares them. There are three kinds:
- Event sharing — The app sends named events from your organisation to the publisher’s company, for example a logistics partner hearing about new orders. Each declared event becomes one grant from your organisation to the publisher.
- App-to-app dependencies — The app needs to call specific tools from another marketplace app installed in your organisation. Each named tool becomes one grant between the two installations.
- Integration dependencies — The app needs to call tools on one of your connected integrations. Today only Shopify is supported. The app uses your one connected account; if you have several, an install from the Apps page fails, and an agent installing the app can name the account to use.
Installing the app is the initial consent: confirming the install activates these grants. The install consent screen asks you to sign off on interface connections, fulfilment services and secrets; the grants above are not listed there one by one.
Managing grants
Section titled “Managing grants”Grants are managed on the installed app’s own page, which the Open button on the Apps page reaches for apps that ship their own pages. For other apps, use the MCP grant tools below. The page shows up to two panels, each only when it has something in it:
- Cross-tenant grant decisions — Grants waiting on your approval or confirmation.
- Cross-tenant tool grants — Grants currently in force, with pause and resume controls.
Only owners and admins of the granting organisation can act on grants.
Pause and resume
Section titled “Pause and resume”Pausing an event or app-to-app grant immediately blocks it — calls fail until you resume. Pausing an integration grant does not block calls today. Use this when you want to temporarily cut off an app’s access without losing the grant’s history or having to re-consent later. Resuming restores access immediately.
Approving new permissions from app updates
Section titled “Approving new permissions from app updates”When a publisher ships a new app version that adds app-to-app tools or events, the new grants are created in a pending-review state. They do not work until you approve them — everything the app could already do keeps working, but the new capability waits for your decision. From the pending panel you can:
- Approve — The grant becomes active and the new tool can be called.
- Reject — The grant is revoked and the new capability never activates.
Integration tools are the exception: new tools on an integration the app already depends on are added with the update without asking, and integration tools the update drops are removed.
Confirming revocations
Section titled “Confirming revocations”When a new app version removes a tool the app previously held a grant for, the grant enters a pending-revocation state and you are asked to confirm:
- Confirm revocation — The grant is revoked, matching the publisher’s intent.
- Keep — The grant stays active despite the publisher’s removal, for example while you stay pinned to an older app version that still uses it.
How grants are enforced
Section titled “How grants are enforced”Only grants in the active state allow calls. Paused, revoked, and pending grants all fail closed — the platform refuses the dispatch rather than allowing it provisionally (integration grants are the exception noted under Pause and resume). Approving, rejecting and revoking a grant record who acted; pausing and resuming do not. Each call made through a grant is logged and kept for 90 days.
Uninstalling an app revokes all grants tied to its installation automatically; the call log stays for its 90 days.
Next steps
Section titled “Next steps”For the install flow where grants first appear, see Installing Apps.
To declare cross-tenant tools or dependencies in your own apps, see Creating Custom Apps.