Request integration access

Request an integration already held by your organization. An organization owner or admin approves it and attaches your product; you do not reconnect the same external account.

Prerequisites

A product in the organization that owns the connection.
Membership in that product; a viewer can request access.
An organization owner or admin to decide the request.
For MCP, an authenticated credential whose identity meets those checks. These tools use user scope; product-role permission patterns do not grant approval authority.

The example product is Acme. Replace it with the product you want attached.

Step 1 — Find the connection

UI

Open Acme’s Integrations page. In Available in the org, find the provider and external account you need. The page also groups attached connections under Granted by the org and Your own.

MCP

Ask the agent to list connections available to Acme with organization_connectors_list-available. Confirm the provider, external account, and display name before choosing its ID.

This list omits stored credentials and other products’ attachments. If the UI cannot load it, the available group is omitted while the rest of the page remains usable; a missing group alone does not prove that no connections exist.

Step 2 — Request access

UI

Choose Request beside the connection. The row changes to pending. A previously denied connection still offers Request.

MCP

Call organization_connectors_request with the connection’s id and Acme’s productId.

A product can have only one pending request per connection. Another request while it is pending is rejected, as is a request for a connection already attached. Filing the request grants no access.

Step 3 — Have an administrator decide

UI

The organization owner or admin opens Organization → Integrations. On the connection card, Needs your review lists pending requests with the product and date. Choose Approve or Deny.

MCP

Using an identity with organization owner/admin authority, list requests with organization_connectors_list-requests. Resolve the selected request with organization_connectors_approve-request or organization_connectors_deny-request, using connection id and requestId.

Approval creates the attachment as part of the same operation. Denial creates no attachment; the product may submit a new request later.

Verify it works

UI

After approval, confirm the connection appears under Granted by the org on Acme’s Integrations page.

MCP

Read Acme’s attached connections with organization_connectors_list. The approved connection should appear there, rather than only in the available list.

The attachment grants the provider-specific access described in Integrations. For Google Ads, check the pinned account; do not assume attachment opens every account behind the login.

Stale requests

Approval checks that the product still belongs to the connection’s organization. A stale request cannot grant access across organizations. Denial can clear a request that no longer makes sense. Removing the product or connection also clears its requests.

Was this page helpful?