Integration Detail Panel

About this block

Integration Detail Panel is the full GitHub integration page: a Connected badge next to the name, the connecting account shown as acme-org connected by Avery Stone on May 14, 2026, three what-it-does bullets (commits linked, deploy statuses posted, repository activity on the project timeline), and the complete permissions list rendered honestly with scope codes (repo:read, statuses:write) and the explicit note that it cannot read code contents, push, or act outside acme-org. Configure rows cover the repository allowlist and environment mapping. The disconnect row states its consequence before you click: deploy statuses stop posting immediately and linked pull requests lose their project references, reconnecting does not restore them.

Permissions and configure rows are separate arrays. The consequence line on disconnect is the copy that prevents a support ticket at 2 am.

When to use

Reach for this block as the detail page for a single integration, wired to your integration config endpoint and the connected account from your OAuth record. The disconnect action should call your revoke endpoint and redirect back to the gallery.

A natural flow around it on an Application Pro page:

Before

• Integrations gallery

After

• Activity feed
• Settings pages

What you can display

One strong use is the OAuth integration detail page. Other detail panels:

• Disconnected state. Same layout, Connected badge removed, connect button in the header.
• Partner integration. Adds a partner callout and links to the third-party support channel.
• Webhook-based integration. Replaces configure rows with the webhook endpoint and secret fields.

Tip: the permissions list earns trust only if it is the complete list; the block says so explicitly and that line should stay.