skill-permissions

Generate and validate least-privilege AL permission sets for Business Central extensions.

99|28|Updated Oct 15, 2025
One-click install
npx skills add https://github.com/javiarmesto/ALDC-AL-Development-Collection --skill skill-permissions-javiarmesto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-permissions
Source: https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/claude-plugin/skills/skill-permissions
Command: npx skills add https://github.com/javiarmesto/ALDC-AL-Development-Collection --skill skill-permissions-javiarmesto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AL permission design for Business Central can be error-prone and hard to audit. This Skill guides you in creating least-privilege permission sets for extensions, ensuring security and compliance across AL and XML formats.

Core Features & Use Cases

  • Pattern-driven permission design (base/read, user, admin) for BC extensions
  • AL and XML permission set formats with generation and extension support
  • Indirect permissions, test permissions, and HITL governance workflow
  • Documentation and governance artifacts for security reviews

Quick Start

Load the skill when starting a new extension and follow the HITL workflow to generate and refine permission sets.

Frequently Asked Questions about skill-permissions

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

FAQPage Schema
How do I design least-privilege permission sets for Business Central extensions?

Generate and validate AL permission sets for Business Central extensions using least-privilege principles. This Skill applies pattern-driven design for base, user, and admin roles to ensure security and compliance.

What is the difference between AL and XML permission set formats in Business Central?

AL and XML permission set formats define Business Central security roles differently. The Skill guides generation and extension for both formats, covering indirect permissions, test permissions, and safeguards against accidental broad access.

How do I prevent accidental broad access when creating BC permission sets?

Prevent accidental broad access in BC permission sets by applying least-privilege principles and following a human-in-the-loop gating workflow. This validates indirect permissions and generates governance artifacts for security reviews.

Does this approach support permission set extensions for existing Business Central roles?

Yes, least-privilege permission design supports permission set extensions for existing Business Central roles. It applies to security reviews and updates, ensuring indirect and test permissions meet governance requirements.

When do I need human-in-the-loop gating for AL permission design?

You need human-in-the-loop gating for AL permission design during security reviews, new extension creation, and updates to existing roles. This workflow ensures permission sets are validated and documented before deployment.