epic-permissions

Implement Role-Based Access Control in the Epic Stack framework.

Updated May 18, 2026

Search Tags:#security #authentication #access control #permissions #rbac #epic stack

Ready to run

npx skills add https://github.com/mbdeaton/phys-notes --skill epic-permissions-mbdeaton

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: epic-permissions
Source: https://github.com/mbdeaton/phys-notes/tree/main/docs/skills/epic-permissions
Command: npx skills add https://github.com/mbdeaton/phys-notes --skill epic-permissions-mbdeaton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to implementing and managing Role-Based Access Control (RBAC) within the Epic Stack framework, ensuring secure and granular access to application features.

Core Features & Use Cases

RBAC Implementation: Learn how to define roles, permissions, and assign them to users.
Server-Side Validation: Securely validate user permissions on the backend for critical actions.
Client-Side UI Control: Conditionally render UI elements based on user permissions.
Use Case: Restrict access to an admin dashboard, ensuring only users with the 'admin' role can view it, while allowing standard users to only manage their own data.

Quick Start

Use the epic-permissions skill to learn how to protect a server-side action with a specific permission.

Frequently Asked Questions about epic-permissions

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

FAQPage Schema

How do I implement role-based access control in an Epic Stack application?▼

To implement role-based access control in the Epic Stack, define permission structures using the action:entity:access format, create Prisma schema models for Role and Permission, and assign roles to users to manage granular feature access.

How do I validate user permissions on the server in the Epic Stack?▼

Server-side permission validation in the Epic Stack uses the requireUserWithPermission and requireUserWithRole functions to securely restrict backend actions and ensure only authorized users can execute critical operations.

Can I conditionally render UI components based on user roles in the Epic Stack?▼

Yes, you can control client-side UI rendering in the Epic Stack by using the userHasPermission and userHasRole functions to conditionally display elements based on the current user's assigned permissions.

What format is used to define permission structures in the Epic Stack?▼

Permission structures in the Epic Stack are defined using an action:entity:access format, which allows granular mapping of specific user actions to application entities for precise access control management.

Does the Epic Stack use Prisma to manage RBAC roles and permissions?▼

Yes, the Epic Stack uses Prisma schema models to manage RBAC, providing structured database definitions for Role and Permission entities that enable persistent storage and assignment of user access rights.

What is the best way to restrict access to an admin dashboard in the Epic Stack?▼

The best way to restrict admin dashboard access in the Epic Stack is combining server-side validation using requireUserWithRole with client-side checks via userHasRole, ensuring only users with the admin role can view or interact with protected features.