Atlassian UX Patterns
Real screenshots and analysis of how Atlassian handles empty states, error states, and permissions. See exactly how they implement these patterns across their product.
Atlassian maintains a unified design language across Jira, Confluence, and its broader product suite through the Atlassian Design System. This ecosystem approach means UX patterns must stay consistent across products with very different purposes — issue tracking, documentation, and team collaboration. Their system states reflect this enterprise-scale thinking: error messages, empty states, and permission models need to work coherently whether you're in a Jira board or a Confluence wiki.
Patterns
Empty States
119 empty state examples from Notion, Slack, Figma & 7 more. Visual patterns, microcopy analysis, and decision frameworks.
View examples
Error States
83 error state examples from 10 enterprise systems. Delivery patterns, microcopy analysis, and recovery frameworks.
View examples
Permission & Access Control
How 10 enterprise systems handle permissions—152 instances across invite flows, role models, access control, and destructive actions.
View examples