1c-roles

Create and analyze 1C configuration roles from Rights.xml and JSON DSL definitions.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill 1c-roles-pavelvdo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 1c-roles
Source: https://github.com/pavelvdo/universal-xml-exchange2/tree/main/.cursor/skills/1c-roles
Command: npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill 1c-roles-pavelvdo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Defining access rights in 1C configurations requires hand-editing verbose Rights.xml files with hundreds of rights entries, RLS restrictions, and templates, which is error-prone and slow. This Skill generates role files from compact descriptions and compresses existing roles into readable summaries. ## Core Features & Use Cases - Role Creation: Generates role metadata (RoleName.xml) and Rights.xml from a rights description, with templates for common rights sets per object type (Catalog, Document, Register, etc.). - Rights Analysis: Parses an existing Rights.xml and outputs a compact summary of allowed/denied rights grouped by object type, including RLS restrictions and templates. - RLS Support: Builds row-level security restrictions and restriction templates with correct XML escaping. - Use Case: When adding a new role for a scheduled job, define the needed objects and rights, compile the role files, register the role in Configuration.xml, then verify the result with the info analyzer. ## Quick Start Ask the assistant to create a 1C role named MyRole with read access to the Currencies catalog and full access to the CurrencyRates information register in the Roles directory.

Frequently Asked Questions about 1c-roles

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

FAQPage Schema
How do I create a 1C role with specific access rights?▼

Define the rights per metadata object using the documented rights sets, then generate RoleName.xml metadata and Ext/Rights.xml with the compile instructions. Finally register the role by adding it to the ChildObjects section of Configuration.xml.

How to analyze rights in an existing 1C Rights.xml file?▼

Run the role-info PowerShell script with the -RightsPath parameter pointing to the role's Rights.xml. It outputs a compact summary of allowed rights grouped by object type, plus RLS restrictions and templates, compressing thousands of XML lines into 50-150 lines.

Does the role analyzer support RLS restrictions in 1C?▼

Yes, rights with restrictionByCondition are marked with an [RLS] suffix in the output, and the summary lists the total number of RLS restrictions and the restriction template names defined at the end of Rights.xml.

Why does the role-info script output corrupted Cyrillic characters?▼

Direct console output can corrupt Cyrillic text due to encoding. Always use the -OutFile parameter to write results to a UTF-8 BOM file and read it with the file reading tool instead of relying on console output.

Which 1C metadata types cannot have rights in a role?▼

Enum, FunctionalOption, DefinedType, CommonModule, CommonPicture, and CommonTemplate do not appear in Rights.xml. Rights are only defined for data objects like catalogs, documents, registers, constants, and configuration-level rights.

What rights does a 1C scheduled job role need?▼

Background jobs only need programmatic rights such as Read, Insert, Update, Delete, and Posting. They do not require Interactive, View, Edit rights or configuration rights like ThinClient and WebClient.