Steel structure repaired component archive parent folder permission checklist

A steel structure repaired component archive parent folder permission checklist helps EPC teams verify the folder level above the repaired component record. The final file may look correct, but if the parent folder is open to the wrong group, repair photos, NCR closeout files, engineering dispositions, and owner acceptance evidence may still be exposed.

This checklist is written for document controllers, quality managers, site closeout teams, and engineering reviewers who need to prove that final archive access is controlled by the project access matrix, not by an old parent folder created during review.

1. Identify every parent folder above the repair record

Start with the final archive link and work upward. Many teams check only the file, but the real access rule may sit two or three folder levels above the file.

• Record the exact final archive URL or storage path for the repaired component record.
• List the component folder, repair package folder, quality folder, project folder, and handover folder above it.
• Identify which folder actually controls access inheritance.
• Check whether any parent folder was copied from a temporary review area.
• Check whether the parent folder contains records from multiple repair cases with different access needs.

For inherited access review, use the archive inherited sharing checklist.

2. Compare parent folder access with archive purpose

Every parent folder should have a clear purpose. A working review folder, final archive folder, owner handover folder, and engineering disposition folder should not all use the same permission rule by default.

For access rules, use the archive access control checklist.

3. Check broad groups and expired users at parent level

Parent folders often contain broad project groups because they were created early in the project. Those groups may no longer be suitable for final repaired component archives.

• Check whether all project users, all site users, or temporary reviewers can access the parent folder.
• Check whether procurement, logistics, or subcontractor users can open restricted quality evidence.
• Check whether expired project users remain inside a group inherited by the parent folder.
• Check whether owner users can see records beyond their handover scope.
• Record every group that appears at parent level but is not in the final access matrix.

For periodic user checks, use the archive permission review checklist.

4. Decide whether the parent folder should be split

Sometimes the parent folder is too broad because it mixes file types with different audiences. In that case, changing one permission setting may not be enough. The archive may need separate final evidence, technical disposition, internal comments, and owner handover folders.

For link migration after splitting folders, use the archive link migration checklist.

5. Test file access after parent folder changes

Changing parent folder permission can affect many files at once. Retest the actual repaired component records, not only the folder page, before closing the change.

• Test a final repair record that should remain available to the owner.
• Test a restricted engineering disposition that should not open for general users.
• Test a repair photo folder that quality users need to retrieve.
• Test an expired user or removed review account.
• Test a site user who should only see installation-relevant closeout evidence.
• Test archive index links and old transmittal links after the permission change.

For access testing, use the archive access retest checklist.

6. Update indexes, registers, and closeout references

Parent folder corrections often change retrieval routes. If the archive index still points to the old broad folder, users may continue to request access through the wrong path.

• Update archive indexes with the correct final folder or file route.
• Update repair registers, NCR closeout logs, and owner acceptance records if links changed.
• Record old parent-folder paths that were retired, restricted, or split.
• Check for broken links after moving records away from the old parent folder.
• Attach a correction note explaining how parent-folder access was changed.

For broken link control, use the archive broken link checklist.

7. Record parent folder permission evidence

The closeout record should prove that parent-folder access was checked, corrected if needed, and retested. Without this record, future teams may not understand why access changed or why a broad folder was split.

• Record parent folder path, permission owner, component mark, repair number, and evidence type.
• Record the original parent-folder groups and the final approved access matrix.
• Record whether the folder was retained, restricted, split, or replaced by a final archive route.
• Record approval owner, change date, and access retest result.
• Attach evidence showing approved users can retrieve the record and unapproved users cannot.

For audit history, use the repaired component audit trail checklist.

Final parent folder permission checklist

Before accepting a repaired component archive, confirm:

• Every parent folder above the repair record was mapped.
• Parent folder purpose was checked against the archive access requirement.
• Broad groups, temporary reviewers, expired users, and unrelated roles were reviewed.
• Mixed-audience folders were split or restricted where needed.
• Owner, quality, engineering, site, anonymous, and expired-user access was retested.
• Indexes, registers, and closeout references were updated after permission changes.
• The parent-folder permission decision and retest evidence were logged.

Red flags in parent folder permissions

• A final repaired component file inherits access from an old review folder.
• The parent folder includes final evidence, internal comments, and technical dispositions together.
• General project users can open restricted repair records because they are in a parent folder group.
• Owner handover access exposes records from unrelated repair cases.
• After splitting folders, the archive index still points to the retired parent folder.
• No retest proves that parent-folder changes preserved required retrieval.

Buyer note: Parent folder permissions should be reviewed before repaired component archive acceptance. EPC buyers should require folder-path mapping, group comparison, folder split decisions, access retesting, and final index updates.