Open Source Platform for DTC, B2B Commerce, Marketplaces & Omnichannel. REST APIs, TypeScript SDKs, and production-ready Next.js storefront. Self-host it. Own your data. No vendor lock-in. Zero platform fees.
Ruby b2b-commercee-commerceecommerceecommerce-apiecommerce-frameworkecommerce-platformheadlessheadless-commerceheadless-ecommercemarketplacemulti-tenantmulti-vendormulti-vendor-ecommerceopen-sourcespree-commerce
import type { ReactNode } from 'react'
import type { ActionName, SubjectName } from '../lib/permissions'
import { usePermissions } from '../providers/permission-provider'
interface CanProps {
/** Action name (e.g. "update", "destroy", "manage") */
I: ActionName
/** Subject short name (e.g. "product") — see `Subject` */
a: SubjectName
children: ReactNode
fallback?: ReactNode
}
/**
* Declarative permission check. Renders `children` if the current user
* can perform `I` on `a`, otherwise renders `fallback` (or nothing).
*
* Example:
* <Can I="destroy" a={Subject.Product}>
* <Button onClick={handleDelete}>Delete</Button>
* </Can>
*
* Note: This is purely for UX. The backend still enforces CanCanCan
* `authorize!` on every request — never rely on the frontend check
* for security.
*/
export function Can({ I, a, children, fallback = null }: CanProps) {
const { permissions } = usePermissions()
return <>{permissions.can(I, a) ? children : fallback}</>
}