useHasPermission
Check one or many permissions.
Import
TypeScript
import { useHasPermission } from '@/hooks';API
Signature
useHasPermission(required, mode? 'all'|'any') → boolean
When to use
Use useHasPermission instead of re-implementing the same pattern in multiple components.
SSR / Next.js
Provider can wrap client layouts; seed isLoading during session hydrate.
Live playground
Edit the example and see it run against the real @/hooks package in this app.
Live playgroundEdit · run with real
@/hooks · useHasPermissionEditor
function EditButton() { const canEdit = useHasPermission('posts:edit'); if (!canEdit) return null; return <button>Edit</button>; }
Preview
Implementation source
Full library source for useHasPermission — copy into your project when you are not installing a package yet.
hooks/auth/useHasPermission.ts
import { useMemo } from 'react';
import { usePermissions } from './usePermissions';
/** Check one or more permissions (default: all required). */
export function useHasPermission(
required: string | string[],
mode: 'all' | 'any' = 'all',
): boolean {
const permissions = usePermissions();
return useMemo(() => {
const list = Array.isArray(required) ? required : [required];
if (list.length === 0) return true;
return mode === 'all'
? list.every((p) => permissions.includes(p))
: list.some((p) => permissions.includes(p));
}, [permissions, required, mode]);
}
Copy-paste example
useHasPermission.example.tsx
'use client';
import { useHasPermission } from '@/hooks';
export function EditButton() {
const canEdit = useHasPermission('posts:edit');
if (!canEdit) return null;
return <button>Edit</button>;
}Production checklist
- Called only from Client Components or other custom hooks
- Type parameters filled in (e.g.
useFetch<User[]>) - Tip: Wrap the tree with AuthProvider and pass your session shape — keep it generic.
- Source of truth: open
hooks/auth/useHasPermission.tsfor implementation details