Search blocks by description or jump to a page.
The invite named, inviter, role, what it grants, and the days left to accept.
The source for every Application block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
Accept Invite Page names the inviter with her avatar and email, priya@acme.com, and the role granted as a Badge: Admin. A muted panel below the role line lists what Admin can actually do in three concrete bullets: invite and remove members, manage billing and plan changes, configure SSO and security policies. The two action buttons are Accept invite and a ghost Decline. The note below Decline is direct: it needs no reason, Priya only sees that you said no, nothing else. The footer states the expiry math in tabular-nums: invites expire after 7 days, this one has 5 days left.
Permissions are a const array, one item per bullet, so swapping the role just means swapping the array. The decline note is the microcopy that stops users worrying about social cost before they click it.
Reach for this block as the landing page for invite tokens, wired to your invite lookup endpoint and your role model. Read the role from the token, swap the permissions array to match, and compute the days-left from the token timestamp.
A natural flow around it on an Application Pro page:
Before
After
One strong use is a workspace Admin invite. Other shapes:
Tip: list what the role can do, not what it is; a badge that says Admin tells the invitee nothing until the bullets answer the real question.