Permission required
Not an error — the page works, the viewer just cannot see it.
Live preview
Source
This exact file renders the preview above.
components/blocks/sections/empty/permission-required.tsx
components/ui/empty-state.tsx
components/ui/alert.tsx
Demo source — adapt to your project. Foundry is not published as a package.
Usage
Naming the missing permission and who can grant it turns a dead end into a message the user can forward, which is the only useful outcome of this screen.
- State the viewer's current role; 'access denied' without it is unactionable.
- Name the people who can grant access if you can.
Variants and states
Every entry below is a genuine difference in behaviour or layout, and every one of them is visible in the preview above.
- Named permission
- Current role
- Who-can-grant note
Accessibility
- Not an error role
- This is a status, not an alert — nothing has failed.
- Actionable copy
- The request action leads to a real flow.
Foundry implements published ARIA patterns and is tested against them. No WCAG certification is claimed — see the accessibility documentation for what is and is not covered.
Related
All sections404 section
A missing page that still offers the real top-level destinations.
starterFeatured3 variantsEmpty state
The three-part empty state — what is missing, why, and the single most likely next action.
starter4 variantsDetailed contact
Routing metadata alongside the message, so an enquiry reaches the right team without triage.
starter4 variants