Optimistic vs Defensive Permission Checks
What you'll learn: You'll understand when to show UI features first and check permissions later versus checking permissions before revealing anything.
The Two Strategies
When building permission-aware interfaces, you face a timing decision: do you show features immediately and hide them if permission checks fail (optimistic), or do you wait for permission confirmation before displaying anything (defensive)?
Optimistic permission checks render UI elements immediately, assuming the user likely has access. Permission verification happens asynchronously in the background. If the check fails, elements disappear or become disabled.
// Optimistic: show first, check later
function EditButton() {
const [canEdit, setCanEdit] = useState(true); // assume yes
useEffect(() => {
checkPermission('document:edit').then(setCanEdit);
}, []);
return canEdit ? <button>Edit</button> : null;
}
Defensive permission checks wait for verification before rendering anything. The UI remains in a loading state until permissions are confirmed.
// Defensive: check first, show later
function EditButton() {
const [canEdit, setCanEdit] = useState(null); // unknown
useEffect(() => {
checkPermission('document:edit').then(setCanEdit);
}, []);
if (canEdit === null) return <Spinner />;
return canEdit ? <button>Edit</button> : null;
}
When to Use Each
Use optimistic checks when:
- Permission failures are rare (most users have access)
- Instant UI rendering improves perceived performance
- Brief flashing of elements is acceptable
Use defensive checks for:
- Sensitive actions (delete, admin features)
- When unauthorized access visibility creates confusion
- When loading states are better UX than content flashing
Key Takeaway: Optimistic checks prioritize speed and assume success, while defensive checks prioritize accuracy and wait for confirmation—choose based on feature sensitivity and typical user permissions.