Documentation / Settings
Anchoring
Choose independent timestamps or offline-only sealing, and inspect provider status.
On this page
Anchoring is WorkSealed’s name for external timestamping. For an explanation of local seals, timestamp authorities, and how they work together, read Sealing, anchoring, and external Time Stamping Authority (TSA) service.
Anchoring status
For each client, the status section shows:
- Open events: history not yet closed into a sealed block.
- Blocks awaiting receipts: sealed blocks still waiting for timestamps.
- Last anchored time: the most recent anchoring result.
- Provider failure: the most recent failure, when available.
A warning appears if blocks wait beyond the configured warning window.
A receipt proves that a fingerprint existed by a signed time; it does not prove that a person was working at that moment. The work logs and their signed history supply the underlying record context.
Choose a mode
- Anchor to timestamp authorities: request independent RFC 3161 timestamp receipts for sealed audit blocks.
- Offline only: keep local sealing and signing without contacting timestamp authorities. Exports report the absence of an independent timestamp.
Only a fingerprint is sent for timestamping, not client or task names, rates, window titles, or work-log contents. The authority can observe IP address and request time. Choose to apply the mode.
Timestamp authorities
Manage providers in the table:
- Create: choose and fill in Name, URL, and Enabled.
- Change: choose in the row menu.
- Delete: choose in the row menu.
Save the provider dialog, then save the Anchoring page to persist the full configuration.
The setup defaults include FreeTSA, DigiCert, and Sectigo. Use a provider URL that accepts RFC 3161 requests; a normal website URL is not necessarily a timestamp endpoint. Disabling providers changes future requests, not receipts already stored in your evidence.
Advanced settings
Enable Show Advanced Settings to reveal:
| Setting | Effect |
|---|---|
| Block max age (minutes) | Closes a block after this time. Shorter intervals tighten the time bound but can make more requests. |
| Block max events | Closes a block when its event-count cap is reached, even before the age limit. |
| Failure warning after (hours) | Controls how long missing receipts can remain before a warning appears. |
Choose to persist edits, or to return the form to saved values.
Pending receipts during export
If a receipt is pending during export, choose:
- : attempt to obtain the receipt.
- : create a locally signed package that reports the anchor as pending.
After a receipt is obtained, export again to include it. A ZIP already sent to a client does not update itself.
The offline browser verifier checks that a receipt covers the block root and reads its signed time. It does not perform full certificate-chain trust validation; the package README explains additional verification steps.
Need a hand? Contact support.