role-edit

Edits 1C:Enterprise role rights by logical metadata path while preserving RLS and templates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Editing 1C:Enterprise role rights by hand in Rights.xml is error-prone: RLS constraints, templates, and unrelated object blocks can be lost, and physical file paths are hard to locate. This Skill performs typed, transactional edits to an existing role's rights through the unica.role.edit MCP tool using a logical metadata address. ## Core Features & Use Cases - Typed right modification: Set a specific right (setRight with objectName, right, and boolean value) on a role addressed as Role.<Name> within a sourceSet, without touching physical Rights.xml paths. - Safe preview by default: Every call builds a dry-run preview; changes are only applied when dryRun is explicitly set to false. - Preservation guarantees: RLS constraints, templates, global flags, and all other object blocks and rights survive the edit; repeated equivalent operations return changed: false with no write. - Use Case: Revoke the Delete right on Catalog.Демо for role Role.Демо, preview the effect, then apply it in a single transaction while keeping all other permissions intact. ## Quick Start Ask the assistant to use the unica role-edit skill to set the Delete right to false for Catalog.Демо in Role.Демо, first as a dry-run preview and then applied.

Frequently Asked Questions about role-edit

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

FAQPage Schema
How do I change a specific right on a 1C role programmatically?▼

Call the unica.role.edit MCP tool with the sourceSet, a metadataPath like Role.<Name>, and an operations array containing setRight entries with objectName, right, and a boolean value. The call previews changes by default until you pass dryRun: false.

How do I find the sourceSet value for role editing?▼

The sourceSet is the name of a source set defined in v8project.yaml, not a fixed constant. Retrieve it with the unica.project.map tool; values like "main" are only examples.

Does editing a role right preserve RLS and templates?▼

Yes, the writer preserves RLS constraints, templates, global flags, and all other object blocks and rights when applying a change. Setting a right to the role's default value removes that right element along with its RLS, which is platform-standard behavior.

Why does role editing fail with object_not_listed?▼

The writer cannot create a missing object block, so granting a right on an object not yet listed in the role's Rights.xml returns object_not_listed. First add the object to the role using the Configurator or unica.role.compile.

What are the limitations of typed role right editing?▼

Only the setRight operation is supported, and the writer does not model platform right dependencies such as input-by-string requiring view. Rights set to the default value are removed rather than stored, and unsupported combinations fail with diagnostics without partial mutation.