Steel structure repaired component archive owner read only access checklist

A steel structure repaired component archive owner read only access checklist helps EPC teams protect final repair records after owner handover. Once a repaired component record is accepted, the owner may need long-term retrieval, but most owner users do not need edit, delete, upload, rename, or replace rights inside the archive folder.

The goal is simple: give the owner enough access to find accepted repair evidence while preserving the integrity of the final record. If a user can accidentally overwrite a repair photo package, delete an approval note, or move a final folder, the archive is not controlled even if the right files were handed over.

1. Define read-only access before handover

Read-only access should be defined before the folder is released. Do not wait until after handover to discover that owner users can edit files or inherited permissions allow uploads.

• Define which owner roles need view-only access to repaired component records.
• Confirm whether download is allowed or whether browser-only viewing is required.
• Separate read-only retrieval from document-control administration.
• Record the read-only rule in the owner handover folder approval note.
• Keep edit rights limited to named archive administrators.

For the wider access boundary, use the owner access folder checklist.

2. Remove edit rights from owner-facing folders

Owner-facing folders should normally allow viewing and retrieval only. Editing rights should be reserved for controlled corrections, not general owner access.

For folder content control, use the archive final record folder checklist.

3. Protect final repair evidence from replacement

Final repair evidence can lose value if files are replaced without a controlled revision trail. Owner read-only access helps preserve the accepted record exactly as it was handed over.

• Lock final repair summaries after acceptance.
• Protect final inspection reports, release notes, and photo packages from replacement.
• Keep obsolete files in a controlled history folder instead of overwriting final files.
• Use revision notes when a final record must be corrected after handover.
• Record who approved any post-handover file correction.

For archive integrity, use the audit trail checklist.

4. Check inherited edit permissions

Read-only access can fail when a final folder inherits edit rights from a parent workspace. The folder may appear controlled, but broad project groups can still modify records.

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

5. Define a controlled correction route

Read-only access should not prevent legitimate corrections. It should force corrections through a controlled route instead of casual edits inside the owner archive.

• Define who can request a correction to final repaired component records.
• Require an approval note before a handed-over record is replaced or amended.
• Keep the original final file in history unless the project rule requires removal.
• Update the archive index after any approved correction.
• Retest owner read-only access after the correction is completed.

For index updates, use the archive index checklist.

6. Test owner read-only access

Access settings should be tested using the same type of account that the owner will use. A folder administrator opening the files does not prove that owner access is read-only.

• Open the final repair folder using an owner user or test owner account.
• Confirm the user can view the accepted repair record.
• Try to upload, rename, delete, replace, and edit a test file in the folder.
• Confirm restricted engineering and internal draft folders remain inaccessible.
• Save the read-only test result with the folder approval record.

For testing details, use the archive access retest checklist.

7. Record read-only approval

Read-only access should have a record because permissions can change after handover. The approval record helps future document controllers understand what access was intended.

• Record the owner group or user list receiving read-only access.
• Record whether download is allowed or restricted.
• Record denied edit, delete, upload, and replace tests.
• Record exceptions where an owner administrator receives additional rights.
• Record the next permission review date if the archive remains active.

For later checks, use the archive permission review checklist.

Owner read-only access checklist

Before accepting read-only owner access, confirm:

• The owner access purpose is defined before handover.
• Normal owner users cannot edit, delete, move, rename, or replace final repair records.
• Download permission is intentionally allowed or intentionally restricted.
• Inherited parent permissions and shared links do not override read-only rules.
• Corrections after handover must follow a controlled approval route.
• Read-only access was tested using an owner role or test owner account.
• Approval records show access group, test result, exceptions, and review date.

Red flags in read-only owner access

• Owner users can upload or replace files inside the final repair folder.
• Anyone-with-link settings allow edit access to repair evidence.
• Final records can be renamed or moved without document-control approval.
• Inherited parent permissions give owner users contributor access.
• No correction route exists for legitimate post-handover record updates.
• No test proves that owner access is actually read-only.

Buyer note: Read-only owner access protects the value of final repaired-component evidence. EPC buyers should require view access, controlled download rules, blocked edit rights, inherited-permission checks, correction workflow, and access test evidence before accepting a repaired steel structure archive.