role-info

Use a PowerShell script to parse the 1C Rights.xml file, aggregate allowed rights by object type, and emit a compact textual report that highlights RLS restrictions for quick role auditing.

Yes, you can view denied rights during a 1C role audit by enabling the ShowDenied parameter in the PowerShell script, which then includes denied permissions alongside the default allowed rights in the output report.

The role rights parser supports pagination via the -Limit and -Offset parameters in the PowerShell script, allowing you to process large 1C Rights.xml files in manageable chunks and output paginated UTF-8 text.

RLS restrictions are displayed as informational flags within the compact summary report whenever the parser encounters them in the 1C Rights.xml file, ensuring you immediately see which objects have row-level security applied.

The best way to get a compact summary of 1C role rights is to run a PowerShell parser against the Roles/.../Ext/Rights.xml file, which aggregates objects and outputs only the allowed permissions in a concise UTF-8 text format.

Yes, you need the 1C role definition stored under the Roles/.../Ext/Rights.xml path structure for the parser to correctly locate and process the XML file to generate your role rights summary.