config-permissions

Create a catalog of permission codes with module, action, and optional scope.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Adrinc/camsys --skill config-permissions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: config-permissions
Source: https://github.com/Adrinc/camsys/tree/main/.agent/skills/config-permissions
Command: npx skills add https://github.com/Adrinc/camsys --skill config-permissions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Granular permission management is often hard to scale across modules and tenants; this skill provides a structured approach to define, organize, and evolve a safe permission catalog that complements config-roles.

Core Features & Use Cases

  • Dynamic creation and removal of granular permissions with module-scoped grouping
  • UI-ready permission catalog organized by module, with visual cues for system vs custom permissions
  • Tenant-aware permission definitions allowing per-tenant customization and isolation
  • Seamless integration with existing config-roles to compose user access controls

Quick Start

Create a new module-level permission for a specific action and optional scope to enable fine-grained access control.

Frequently Asked Questions about config-permissions

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

FAQPage Schema
How do I define granular permissions for a multi-tenant backend system?

Granular permissions are defined by creating a catalog of permission codes structured with module, action, and optional scope, enabling tenant-aware access control and isolation across backend modules.

What is the best way to organize a permission catalog by module for frontend UI?

A permission catalog organized by module provides UI-ready grouping with visual cues distinguishing system permissions from custom ones, allowing dynamic creation and pruning of access controls across tenants.

Can I dynamically create and prune module-scoped permissions across multiple tenants?

Module-scoped permissions can be dynamically created, updated, and pruned across multiple tenants using standard SQL queries and a backing schema with built-in safety checks.

Does config-permissions work with existing role definitions for backend access control?

Config-permissions integrates with config-roles to compose user access controls, allowing you to build comprehensive authorization by combining granular permission codes with existing role definitions.

How do I implement SQL queries for standard CRUD operations on a permission schema?

SQL queries for standard create, read, update, and delete operations are implemented on a backing permission schema, utilizing module grouping and safety checks to prevent unauthorized modifications.