f4e1f9d218
The Phase B plan (commit 8eb2c2de) listed 12 modules to sweep, but the
codebase has 13 more modules with ACL CSVs referencing the old role
group xmlids. Backward-compat (Phase A's implied_ids chains) keeps
these working today, but the old groups will be deleted after the
30-day rollback window — so the sweep must cover ALL modules with
plating-group ACL refs to avoid post-rollback breakage.
Sweeps: batch, bridge_documents, bridge_maintenance, bridge_mrp
(uninstalled but file present), bridge_quality (planned removal),
bridge_sign, compliance, culture (retired), kpi, logistics,
notifications, portal, reports.
Pattern matches the original sweep:
group_fusion_plating_operator → group_fp_technician
group_fusion_plating_supervisor → group_fp_shop_manager_v2
group_fusion_plating_manager → group_fp_manager
group_fusion_plating_admin → group_fp_owner
group_fp_accounting → group_fp_manager
group_fp_receiving → group_fp_shop_manager_v2
group_fp_estimator → group_fp_sales_rep
group_fp_shop_manager (legacy) → group_fp_manager
cgp_officer → group_fp_quality_manager
cgp_designated_official → group_fp_owner
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
7 lines
776 B
CSV
7 lines
776 B
CSV
id,name,model_id:id,group_id:id,perm_read,perm_write,perm_create,perm_unlink
|
|
access_fp_notification_template_operator,fp.notification.template.operator,model_fp_notification_template,fusion_plating.group_fp_technician,1,0,0,0
|
|
access_fp_notification_template_manager,fp.notification.template.manager,model_fp_notification_template,fusion_plating.group_fp_manager,1,1,1,1
|
|
access_fp_notification_log_operator,fp.notification.log.operator,model_fp_notification_log,fusion_plating.group_fp_technician,1,0,0,0
|
|
access_fp_notification_log_supervisor,fp.notification.log.supervisor,model_fp_notification_log,fusion_plating.group_fp_shop_manager_v2,1,1,1,0
|
|
access_fp_notification_log_manager,fp.notification.log.manager,model_fp_notification_log,fusion_plating.group_fp_manager,1,1,1,1
|