Archive, delete, and history

Archive and delete serve different purposes. Archive keeps a readable record outside the default active list; delete removes the record and its accessible detail.

Overview

Use archive for queue cleanup and retention. Use deletion only when the record genuinely should not remain in SolarSENS. The timeline can help explain changes while the parent record still exists, but it is best-effort rather than a guaranteed audit ledger.

Action	Use it when	Record remains readable?	Reversal path	Access boundary
Archive	A retained record should leave the default active list.	Yes, for users with plant/read access.	Unarchive returns the record to active handling as described below.	Permission-dependent and not universally management-only.
Request Delete	A user without management-level delete access believes the record should be removed.	Yes, while the request is pending.	An admin or supervisor can reject the request with a reason.	One pending request can exist for a work order at a time.
Direct or approved delete	The record should not remain in SolarSENS.	No. The detail and timeline are removed from access.	None from the interface.	Admin or supervisor access is required.
Timeline review	You need context for changes while the work order exists.	Yes, while the parent record exists.	Not applicable.	Treat it as operational context, not a guaranteed audit ledger.

Archive and unarchive

Open an eligible active or resolved work order.
Select Archive to remove it from the default active list.
Retrieve archived work with the Archived status filter when you need its detail or timeline.
Select Unarchive when the record needs active handling again.

Unarchive returns the work order to Assigned only when archive history identifies Assigned as its prior display status. Otherwise it returns as New. A formerly resolved record does not return to Resolved.

Archive availability is permission-dependent and is not universally management-only. Pending drafts cannot be archived.

Governed deletion

Users without management-level delete access can select Request Delete. One pending request can exist for a work order at a time.

Admin or supervisor users can:

delete a readable work order directly
review pending delete requests
approve a request, permanently removing the record
reject a request with a required reason

Use archive when retention is appropriate. Approved or direct deletion is destructive and removes access to the work-order detail and timeline.

Timeline and history

Use the timeline for operational context while the work order exists. It can help explain ownership, lifecycle, shutdown, attachment, and optional subtask changes, but it is not a guaranteed audit ledger. See Core records and entities for its reliability limits.

Expected outcomes

retained records no longer clutter the default active list
archived detail remains available to users with plant/read access
destructive deletion follows the appropriate request or elevated path
timeline context helps explain ownership and lifecycle changes while the record exists