role-info

Parses 1C role Rights.xml files into structured permission, RLS, and template summaries.

1|2|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill role-info-ingvarconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: role-info
Source: https://github.com/IngvarConsulting/unica-marketplace/tree/main/plugins/unica/skills/role-info
Command: npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill role-info-ingvarconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Auditing 1C:Enterprise role permissions requires manually reading verbose Rights.xml files, making it hard to see which objects and actions a role grants, which rights are denied, and where record-level security (RLS) restrictions apply. ## Core Features & Use Cases - Structured rights summary: Parses Rights.xml and returns objects grouped by kind with allowed and denied rights, RLS restriction flags, totals, and restriction templates. - Flexible role selection: Accepts either a file path to Rights.xml or a logical selector (sourceSet plus metadataPath like Role.<Name>), rejecting conflicting selectors with a selector_conflict error. - Support awareness: Reports vendor support status (supported, extension, removed, notSupported) read from ParentConfigurations.bin. - Use Case: Before modifying a locked vendor role, run the audit to confirm which rights are denied and which objects carry RLS restrictions, then record a release-support decision instead of editing rights directly. ## Quick Start Ask the assistant to run /role-info with the path to the role's Rights.xml file, for example Roles/Accountant/Ext/Rights.xml, to get a compact summary of its permissions and RLS restrictions.

Frequently Asked Questions about role-info

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

FAQPage Schema
How do I audit role permissions in a 1C:Enterprise configuration?▼

Run the role audit with the path to the role's Rights.xml file, typically Roles/<RoleName>/Ext/Rights.xml. The result groups objects by kind and lists allowed and denied rights, RLS restriction flags, totals, and restriction templates.

How to check RLS restrictions on a 1C role?▼

The parsed output marks each right with a restricted flag when record-level security applies and lists restrictedObjects plus the role's restriction templates. This shows exactly which objects have row-level access limits without reading the XML manually.

Can I select a 1C role by metadata path instead of file path?▼

Yes, pass sourceSet plus a logical metadataPath such as Role.<Name> instead of RightsPath. Exactly one selector style is allowed; passing both is rejected with a selector_conflict error.

Why does the role audit return a selector_conflict error?▼

The error occurs when both a Rights.xml file path and a logical selector (sourceSet with metadataPath) are provided in the same call. Remove one of the two selectors and retry with a single target.

Does the role audit show denied rights or only granted ones?▼

Denied rights are always included alongside allowed ones in the denied field, grouped the same way by object kind. An empty denied list means the role has no denied rights, not that they were skipped.