Documentation verification scope
This replacement site builds on an existing manual draft. Having a page is not the same as executing and verifying every feature. The label above each guide distinguishes its verification level.
Verification labels#
| Label | Meaning |
|---|---|
| Production screen checked | The relevant production menu was inspected with the test account. This does not mean payment approval, processing completion, or recipient acceptance was verified |
| Existing draft · see verification scope | Adapted from the existing manual. Further checks may be needed for the actual account, role, and options |
Basis for this review#
- Environment: production at
works.letr.ai - Review date: November 13, 2026
- Languages: Korean and English documentation with production screenshots in the corresponding UI language. Not every feature has a screenshot.
- Screens: 16 captures per language, taken at a real 1464 × 1064 desktop viewport. Narrow screenshots were not upscaled and relabeled as desktop captures.
- Authentication: the user-authorized test account. Its address and the real invitation recipient are not published.
- Historical screenshots that have not passed privacy review are excluded from the public build.
Executed actions and limits#
A member invitation was sent to the designated test recipient, and the Email sent confirmation was observed. Inbox delivery, following the invitation link, and permissions after acceptance are separate checks.
Inspecting billing is different from an actual card authorization or charge. A purchase or credit-consuming operation is not marked complete without a confirmed result. Current product screens are the source of truth for prices and limits.
An English-to-Korean Document Globalization project was created from the sample DOCX, and all three translated sentences were inspected. A sentence was activated and edited; the edit persisted after leaving and reopening the project.
Credit top-up did not complete. Selecting the smallest package, 5 credits ($5), resulted in a server error (500) while requesting the payment page. Card approval and a credit increase were not confirmed. The action was not retried to avoid duplicate payment.
Destructive deletion, account closure, and public distribution through external services are not performed just to write documentation.
Scope of the examples#
Task examples are fictional scenarios for learning the features. Sample workflow checked applies only to the three-sentence document creation/translation and sentence edit/reopen examples. Other service, asset, collaboration, and delivery scenarios are illustrative examples based on the existing feature descriptions. They do not claim new execution, successful payment, or completed delivery.
No invitation, payment, service execution, project creation, or external sharing was repeated to add these examples.
Screenshot anonymization#
Public screenshots mask or replace names, emails, workspace identifiers, profile pictures, and original media. Opaque masks are used instead of weak blur. Do not interpret sample values as actual user information.
The official product logo and navigation remain visible. Real asset/project filenames and small collaborator avatars are masked too. Editor examples display only this manual's fictional sample sentences.
When a screen differs#
Roles, plans, and gradual rollouts can change which menus appear. Use the current product screen for exact button labels and rates. See Troubleshooting.
Account and contact details in screenshots are anonymized. Menus may vary by role and release.