erpnext-errors-permissions

Secure has_permission hooks in ERPNext require standardized patterns that return None to deny or defer access, ensuring they never accidentally grant permission. This Skill provides battle-tested hook implementations with robust error handling and safe fallbacks for production reliability.

Safe permission_query_conditions in Frappe require wrapping database queries in try/except blocks with SQL escaping and safe fallbacks. This approach prevents silent failures and security gaps while maintaining consistent query filtering across ERPNext modules.

Silent permission failures in ERPNext occur when has_permission hooks lack proper try/except wrapping or return inconsistent values. Using consistent PermissionError usage and standardized error patterns ensures failures are caught, logged, and surfaced correctly.

Yes, these permission error handling patterns apply to document-level and API permission checks across all ERPNext modules. They provide consistent messaging, security-first auditing, and denial event logging for comprehensive coverage.

Audit logging for Frappe permission denial events requires security-first logging patterns that capture denial actions and create audit trails. This Skill implements structured logging alongside standardized permission checks to ensure production reliability and traceability.