Permissions & Suggestion Engine

Step 5 — Permissions

The Permissions step assigns permission levels to roles on each folder. The suggestion engine analyses your folder structure and matrix to recommend permissions, then role group consolidation reduces the total number of rules.

Strategy presets

Choose a preset to set baseline permission levels. Each preset defines four match tiers:

You can also use Custom mode to override any tier individually.

How match tiers work

The engine analyses each folder path to detect which party (L1) and discipline (L3) it belongs to. For each role-folder combination, it determines which tier applies:

1. Org + Discipline — The role's L1 and L3 both match the folder (highest access).
2. Org Only — The role's L1 matches but L3 doesn't.
3. Discipline Only — The role's L3 matches but L1 doesn't.
4. No Match — Neither L1 nor L3 matches (baseline access).

AI-enhanced function overrides

Click Enhance Levels to get AI-suggested per-function (L2) overrides. For example, the AI might suggest that "BIM Lead" gets Full Control at the org+discipline tier while "General" only gets View/Download. A grid shows each L2 function with two dropdowns — one per tier.

Role filter

Three rows of clickable chips (L1, L2, L3) let you control which roles participate in permission generation. Left-click to include only that value; right-click to exclude it (exclusions take priority). A counter shows how many roles are included.

Role group consolidation

When all individual roles covered by a group share the same permission on a folder, the system automatically replaces them with a single group rule. Consolidated entries appear with a purple ring and a tooltip showing how many individual rules were replaced. An info panel shows the total consolidation savings.

Assigning permissions

You can assign permissions in two ways:

• Bulk actions — Select folders using checkboxes, pick a role from the searchable dropdown (grouped into Role Groups, Matrix Roles, and ACC Roles from CSV), choose a permission level, and apply to all selected folders.
• Inline editing — Expand any folder row to see its current permissions and add or remove individual role-permission pairs.

Permission application

Once permissions are configured, they can be applied to ACC. The application process:

1. Resolves folder paths to ACC folder IDs.
2. Resolves role names to ACC role IDs via the project's CSV.
3. Applies permissions in batches (up to 50 per folder) with parallel execution.
4. Reports success and failure counts.