backend-auth

Define backend authentication and authorization rules for Drumr Framework apps.

Updated Sep 16, 2025
One-click install
npx skills add https://github.com/slingr-stack/qa-test-drumr --skill backend-auth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-auth
Source: https://github.com/slingr-stack/qa-test-drumr/tree/main/project-management-app/.agents/skills/backend-auth
Command: npx skills add https://github.com/slingr-stack/qa-test-drumr --skill backend-auth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you secure Drumr backend apps by defining who can see, create, update, execute, and write specific data without leaking permissions across roles or forms.

Core Features & Use Cases

  • Register guest, global, and role-based permissions with app.defineGuestPermissions, app.defineGlobalPermissions, and app.definePermissionsForRole.
  • Model application users with AppUser and enforce action permissions for models, params, and return classes.
  • Handle common backend edge cases such as access/read pairing, File uploads and downloads, immutable audit fields, and relation selectors that must write referenced ids.
  • Use it when building ownership rules, assignee-only actions, or broad admin access with precise deny overrides.

Quick Start

Use this skill to draft or review a backend authorization file for your Drumr app, including role rules, model access, and any required file or relation-selector permissions.

Frequently Asked Questions about backend-auth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define role-based permissions for a backend app?

Define role-based permissions by registering guest, global, and role-specific access rules using app.defineGuestPermissions, app.defineGlobalPermissions, and app.definePermissionsForRole to secure backend app resources.

How do I handle file upload and download access control in my backend?

Handle file upload and download access control by applying permission guards that enforce read and access pairing, ensuring only authorized roles can manage file transfers within the backend authorization rules.

Why does my form submission fail when writing to a related model?

Form submissions fail when relation selectors lack id-only write access to referenced models, requiring correct permission precedence and class-based permission subjects to authorize referenced data persistence.

What is the best way to enforce immutable audit fields with backend authorization?

Enforce immutable audit fields by applying action execution guards within your backend authorization rules, preventing unauthorized role updates to tracked persistence fields during create and edit flows.

Can I use condition-operator syntax for access control rules?

Yes, condition-operator syntax is supported for access control rules, enabling precise deny overrides and assignee-only actions when defining permissions for models, params, and return classes.

Does AppUser modeling support assignee-only action execution?

AppUser modeling supports assignee-only action execution by pairing access and read grants with condition-operator syntax, enforcing ownership rules and restricting action execution guards to authorized users.