Access Denied 403
A centered 403 page with a signed-in identity card, the admin who can grant access, a request action, and account switch controls.
A centered 403 page with a signed-in identity card, the admin who can grant access, a request action, and account switch controls.
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
Access Denied 403 treats a locked page as a routing problem, not a scolding. The mono 403 sits above a human headline, then a body line that draws the important distinction, you are signed in fine, this workspace simply has not granted your account. Below it an identity card names the exact address in session and, in the same frame, the admin who can grant access with a request button beside their avatar.
The admin row is one object worth wiring to whoever actually owns the workspace, so the request lands with the right person instead of a support queue. The switch account and back to workspaces buttons cover the two other real fixes, and a footer line sets the expectation that a request notifies by email and expires.
Reach for this block as the rendered 403 for gated workspace pages, where the person is authenticated but not authorized. It works because it turns a dead end into a single named action, and the tone stays blameless rather than treating access as a fault.
A natural flow around it on a Marketing Pro page:
Before
After
One strong use is the workspace 403 with a named admin. Other variants:
Tip: point the request button at the real workspace owner, not a shared inbox, so the one click actually reaches someone who can say yes.