Legal History Recovery
Separate a failed history check from an explicit acknowledgement.
These images are illustrations of the concept, not screenshots of the actual product.
Overview
This Workspaces concept illustrates two distinct moments in an acknowledgement flow: history that cannot be verified, and a completed history check that leads to a document review. The side-by-side presentation keeps the difference visible instead of treating an unavailable response as proof that a person has never accepted the documents. Both panels use the same Terms & Privacy title and a consistent dialog layout.
The first panel is labelled Verification unavailable. An alert symbol accompanies a clear explanation that acknowledgement history could not be verified. A separate sentence states that Retry checks history without recording acceptance. Retry is the only action in that panel. The underlying navigation is muted, keeping attention on recovery while retaining a sense of where the person is in Workspaces.
The second panel is labelled History checked. It presents a document symbol, a short review instruction and separate Terms of Service and Privacy Policy links. Its I agree button represents an explicit choice after the history check rather than a recovery action. The illustration does not show a saved acknowledgement, an account identity, a receipt, or an assurance about the legal status of the documents.
The footer states the interaction rule: Retry reads history, while acceptance requires an explicit choice. This concept is designed to help members understand what the next action will do and help administrators discuss a blocked onboarding experience without confusing recovery with acceptance. It focuses on the visible decision boundary; document policy, version requirements and the handling of uncertain write outcomes require their own product contracts.
What this concept shows
- Two panels distinguish unavailable verification from a completed history check
- Retry is the only action shown for unavailable history
- Separate document links support review before the explicit I agree choice
- A shared footer explains the difference between reading history and recording a choice
How it works
- Read the verification message in the first panel
- Use Retry to check history without recording acceptance
- After a completed check, review the linked documents in the second panel
- Make an explicit acknowledgement choice when the acceptance dialog applies
Who it's for
- Workspace members
- Workspace administrators
- Product and legal operations teams
Illustrations
1 illustration of this concept. Select one to view it full size.
History Verification and Explicit Choice
The illustration places two Workspaces dialogs side by side. The left panel, Verification unavailable, shows an alert symbol and explains that acknowledgement history could not be verified. Its supporting text says that Retry checks history without recording acceptance, and Retry is its only button. The right panel, History checked, uses a document symbol and asks the person to review the Terms of Service and Privacy Policy before continuing. Both document titles appear as links above an I agree button. Muted navigation remains visible behind each dialog. A footer connects the panels by stating that Retry reads history while acceptance requires an explicit choice. No saved record or real personal information is displayed.
Topics
- acknowledgement history
- onboarding recovery
- explicit consent
- history verification
- terms and privacy
- read-only retry