relational-permissions

Enforce relational permissions on parent and child collections for nested writes.

1|Updated May 26, 2026

Search Tags:#RBAC #database security #relational permissions #permission enforcement #nested writes

Ready to run

npx skills add https://github.com/BaraArdiwinata/hackathon-sima-arome --skill relational-permissions-baraardiwinata

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: relational-permissions
Source: https://github.com/BaraArdiwinata/hackathon-sima-arome/tree/main/.agents/skills/relational-permissions
Command: npx skills add https://github.com/BaraArdiwinata/hackathon-sima-arome --skill relational-permissions-baraardiwinata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that permissions on junction and child collections are enforced at every level, not just the parent, for nested relational writes.

Core Features & Use Cases

Relational Permission Enforcement: Checks permissions on both parent and child collections for create/update/delete operations.
Layered Enforcement Model: Two-layer enforcement model to ensure that only authorized users can modify nested relations.
Use Case: Use this Skill when setting up write access for collections that participate in relational fields or when debugging silent no-ops on nested mutations.

Quick Start

Set up relational permissions for the 'cmp_catalogues' parent collection with 'create' and 'delete' actions on the 'cmp_catalogue_services' child collection.

Frequently Asked Questions about relational-permissions

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

FAQPage Schema

How do I enforce RBAC on nested relational writes in a database?▼

To enforce RBAC on nested relational writes, you must apply permission checks on both parent and child collections. This Skill uses a two-layer enforcement model to ensure only authorized users can modify nested relations during create, update, and delete operations.

Why are silent no-ops happening during my nested relational mutations?▼

Silent no-ops during nested mutations occur when permission enforcement is missing on junction or child collections. Applying relational permission checks across all participating collections prevents these unauthorized write operations from failing silently.

What is the best way to set up write access control for junction collections?▼

The best way to set up write access control for junction collections is implementing a layered enforcement model. This approach explicitly checks permissions on both the parent and child collections before allowing any nested relational write operations.

Do I need to check permissions on child collections separately for relational writes?▼

Yes, you need to check permissions on child collections separately for relational writes. Enforcing permissions only on the parent collection leaves nested writes vulnerable, so a two-layer model is required to secure junction and child records.

Can I use this permission enforcement model for create, update, and delete operations?▼

Yes, you can use this relational permission enforcement model for create, update, and delete operations. It ensures that write access is permission-controlled across all levels of the nested relational hierarchy.

When do I need to enforce relational permissions on nested database structures?▼

You need to enforce relational permissions on nested database structures whenever your collections participate in relational fields. This prevents unauthorized data modification by ensuring write access is verified at every parent and child layer.