frappe-core-permissions

To implement row-level filtering in Frappe without bypassing permissions, use frappe.get_list() for user-facing queries instead of frappe.get_all(), and apply permission_query_conditions hooks to filter list-view rows safely.

Your Frappe has_permission hook breaks standard role permissions because it returns True, overriding standard evaluation. Hooks should only return False to deny access or return None to defer to standard Frappe permission checks.

To prevent SQL injection in Frappe permission_query_conditions hooks, escape all SQL inputs and use proper table prefixes. This ensures that dynamic row-level filtering conditions are securely applied without exposing database vulnerabilities.

Yes, Frappe v16 supports data masking for field-level access control. This Skill applies deterministic patterns across role permissions, user permissions, and perm levels to securely control which fields users can see or mask.

The best way to check document permissions in ERPNext custom scripts is using frappe.has_permission and document permission checks. This enforces backend access control and prevents permission-bypassing operations via ignore_permissions.

You should avoid using ignore_permissions in Frappe document operations whenever user-facing data is involved. Undocumented ignore_permissions bypasses standard access control, leading to insecure permission implementations that fail in production.