nacl-sa-roles

Define system roles and CRUD permissions within a Neo4j graph.

23|2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ITSalt/NaCl --skill nacl-sa-roles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nacl-sa-roles
Source: https://github.com/ITSalt/NaCl/tree/main/nacl-sa-roles
Command: npx skills add https://github.com/ITSalt/NaCl --skill nacl-sa-roles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

System roles and permission management within a Neo4j graph is complex; this skill provides a formal model for SystemRole, HAS_PERMISSION, and MAPPED_TO, enabling consistent governance and traceability across BA and SA layers.

Core Features & Use Cases

  • Define SystemRole nodes and their MAPPED_TO relationships from BusinessRole sources.
  • Build a CRUD permission matrix across DomainEntities with HAS_PERMISSION edges.
  • Manage full lifecycle modes: IMPORT_BA, CREATE, MODIFY, and FULL to align with project maturity.
  • Establish data-scope constraints and actor mappings to UseCases for workflow authorization.

Quick Start

Propose or import BA roles, create SystemRole nodes, define permissions, map roles, and verify the graph coverage.

Frequently Asked Questions about nacl-sa-roles

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

FAQPage Schema
How do I model system roles and permissions in a Neo4j graph database?

Model system roles and permissions in a Neo4j graph by defining SystemRole nodes, HAS_PERMISSION relationships for CRUD matrices, and MAPPED_TO edges from BusinessRole sources to establish governance and traceability.

What is the best way to map business roles to system roles for access control in Neo4j?

Map business roles to system roles by creating MAPPED_TO relationships from BusinessRole sources, enabling consistent governance and traceability across BA and SA architectural layers.

Can I define data-scope constraints and actor mappings for UseCases in Neo4j?

Yes, you can define data-scope constraints and link actors to UseCases within Neo4j to enable workflow authorization and end-to-end security traceability across modules.

How do I manage the permission lifecycle from business analysis to system architecture in a graph database?

Manage the permission lifecycle using IMPORT_BA, CREATE, MODIFY, and FULL modes to align graph database role definitions with project maturity from business analysis to system architecture.

Does Neo4j work for building a CRUD permission matrix across domain entities?

Yes, Neo4j effectively builds a CRUD permission matrix across DomainEntities by using HAS_PERMISSION edges to connect SystemRole nodes for detailed access control planning.

Why define a formal role model in Neo4j instead of using traditional relational database permissions?

A formal role model in Neo4j provides consistent governance and traceability across BA and SA layers, overcoming the complexity of system role and permission management found in traditional relational databases.