Integration Security Panel
A trust focused split with a headline, four security assurances, and a docs link beside an access manager showing granted scopes and a revoke control.
A trust focused split with a headline, four security assurances, and a docs link beside an access manager showing granted scopes and a revoke control.
Search blocks by description or jump to a page.
The source for every Marketing block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Integration Security Panel answers the security question a careful buyer brings to any integration. The left column pairs a headline and lede with four assurances, each a checked tile over a title and a supporting line covering scoped OAuth, encryption, one click revoke, and audit logging, then an outline button to the security overview. The right column is a blueprint of the access manager: a connected app header with its mark and who added it, a list of granted scopes with read or write badges, a revoke control, and an audit footer.
The assurances and scopes are small arrays, so tailoring the claims or the permission list is a copy edit rather than a refactor. The app logo is an abstract inline SVG drawn from currentColor and every surface uses theme tokens, so the section stays legible in light and dark mode without an image file. The panel does the persuading, it is one thing to promise scoped access and another to show the exact scopes with a revoke button sitting right beside them.
Reach for this block when the person who has to approve an integration is not the person excited to install it. Security and IT reviewers want to see permissions, revocation, and an audit trail before they sign off, and putting the access manager on screen answers them without a call. It belongs on an integrations or enterprise page, right where a promising evaluation can stall on a risk question.
A natural flow around it on a Marketing Pro page:
Before
After
The obvious fit is a connected app and its scopes. A few other ways to use the frame:
Tip: name the scopes as plainly as a real consent screen would and keep the revoke control visible, a reviewer trusts the parts of the product they can see themselves controlling.