Productivity & Workflows
Zight Review for Async Work: Screenshots, Videos, and Team Sharing Controls
A fictional support issue becomes two planned screenshots, a complete short-video script, and a written question, followed by a three-creator access and backup decision with actual delivery checks still pending.
Zight is worth evaluating when a work explanation needs annotated still images, a short demonstration, and a controlled way for recipients to review them. Choose a plan that covers the required capture history, recipient access, and approved archive route. Check who can open the generated link and who is blocked before treating delivery as complete.
This LandOffer.ai review checks public documentation and rendered pricing on October 27, 2026. It contains a complete fictional support packet and a team access-and-backup decision. We did not install Zight, record a screen, upload files, change sharing permissions, or test a recipient's access. The packet is an authored storyboard and written explanation, not captured product evidence.

Separate capture convenience from successful delivery
Zight's desktop guide describes screenshots, annotations, screen recordings, webcam recordings, GIFs, and collections. Its web dashboard manages content and settings but has a more limited recording route. Verify the particular device and route rather than assuming the web app reproduces every desktop capability. Desktop and dashboard guide.
A screenshot is useful when the recipient needs to inspect one exact state, field, or error. A video is useful when the sequence matters: what happened before Save, which view refreshed, or how a filter changed the result. Written context identifies the task, expected behavior, and question. Put the issue in the written message so a recipient can decide whether the still images answer it or the action sequence needs watching.
Cloud handling is part of that workflow. Zight says capture content uploads to its cloud, while a desktop option can save local copies of videos. That local-copy option is described for video, not every screenshot and file. Do not assume selecting a folder creates a complete offline archive of everything you share. Storage guide.
Before capturing work material, close unrelated windows and notifications and decide what may be uploaded. Removing unnecessary content from the source view is preferable to hoping a later viewer will overlook it. Any proposed redaction also needs inspection in the delivered artifact; a feature listing alone does not verify the result.
Read the current plans and preserve the history-limit conflict
The rendered pricing page used Share, Create, Collaborate, and Scale. The August plan guide maps older Free, Pro, Team, and Enterprise names to those names and warns that its prices may lag checkout. Use the actual current account and purchase context when reconciling an older review or invoice. Plan-change guide.
The current USD pricing page showed Collaborate at $15 per user monthly or $12 with annual billing. Its calculator began at two seats and displayed $432 per year for three on Annual, versus $45 per month on Monthly. Taxes and checkout were not verified. Current pricing.
The current table listed Share recording length at five minutes and capture-history access as the last 50 captures. However, the May 27 help article says the free Share plan exposes only the newest 25 items, with older items hidden rather than deleted. These descriptions conflict. Confirm the actual account's limit instead of promising either number as a tested entitlement. Share history guide.
Neither access cutoff is a retention policy. A visible item can still be subject to an organization's deletion rules, while an item outside a free access window is not automatically evidence of deletion. Keep capture availability, link accessibility, and the underlying file's lifetime as separate checks.
Completed asset: a screenshot-and-video support packet
Fictional support specialist Rhea receives a question about an internal inventory training app. A demonstration row, D-014, disappears from the Ready list after saving a location. All app states in this storyboard are fictional; they are neither an observed application test nor a Zight capture. The intended recipients are internal application owner Luis and support colleague Mina.
Rhea's completed packet has two planned screenshots, a 2-minute-10-second recording script, and a written question. Every visible value uses demo data. She excludes employee names, real stock numbers, browser account controls, and unrelated notifications from the proposed framing.
| Asset | Exact content in the fictional storyboard | What the recipient should learn |
|---|---|---|
| S1: before Save | Demo row D-014; status Ready; location A-2; Ready filter active | Which row and filter are involved before the change |
| S2: after Save | Ready list no longer shows D-014; switching to All reveals D-014 with status Draft and location A-3 | The row remains present in another view; disappearance from one filter is not proof of deletion |
| V1: short sequence | Select the row, change location, save, inspect Ready, then inspect All | The order of actions and observed state changes within the fiction |
The recording's complete run-of-show is specific enough for another person to prepare the same explanation:
- 0:00–0:20: Introduce the demo environment and the question. Show the Ready filter and row D-014, pointing out location A-2 and status Ready.
- 0:20–0:50: Open the row and change only location to A-3. Show the status before saving. Say that the intended edit is the location, not the workflow state.
- 0:50–1:15: Save once and return to the Ready list. Show that D-014 is absent. Do not describe it as deleted.
- 1:15–1:45: Switch to All and find D-014. Show location A-3 and status Draft. Keep the filter and status visible together so the recipient can distinguish them.
- 1:45–2:10: Ask whether this status transition is intended and where it is documented. State that no application fix or return to Ready has been approved.
Those segments total 130 seconds. The proposed video fits numerically within the displayed five-minute Share recording limit; duration alone does not justify an upgrade. Actual recording, annotation legibility, audio clarity, and upload behavior remain untested.
Finished message accompanying the assets:
Subject: Demo row D-014 moves out of Ready after location save
In the training scenario, changing D-014 from A-2 to A-3 and saving leaves the row visible under All with status Draft. It is no longer visible under Ready. S1 identifies the initial filter and state; S2 shows the row under All. V1 supplies the action order.
Luis, please confirm whether changing location is intended to change the workflow state. If so, please point us to the relevant rule; if not, advise what additional demo evidence you need. We have not established the cause and have not instructed anyone to change production records. Mina will keep the support explanation marked unresolved until that question is answered.
The packet's value is the distinction it preserves. It neither labels a filtered-out row “lost data” nor treats the observed Draft state as an approved workaround. A recipient can answer a precise question without reconstructing the entire situation from narration. No claim is made that Zight generated this explanation or would automatically detect its important qualifiers.

Completed asset: decide the team audience and backup
Rhea, Luis, and Mina would all create visual explanations, so this case counts three creator seats rather than assuming two people are free viewers. Rhea expects to create eighteen packets monthly in her own account, each containing two screenshots and one video: 54 captures for her account alone. Luis and Mina create other material outside this count; their histories are not pooled here. Rhea's 54 exceeds both published free-history descriptions, 25 and 50. Their need to revisit all packets therefore requires a resolved access arrangement, regardless of which free limit actually applies.
The team also requires named internal recipients. The rendered feature table lists specific-person restrictions, private workspace sharing, and password protection under Collaborate and Scale, with dashes under Share and Create. This makes Collaborate the relevant documented candidate for this requirement, subject to an authorized access check. It does not establish that a particular account is already configured correctly. Plan comparison.
Their completed delivery record distinguishes the intended state from work still pending:
| Item or decision | Fictional approved requirement | Disposition and remaining check |
|---|---|---|
| S1, S2, V1 originals | Rhea owns the demo evidence; Luis and Mina review | Keep internal; no public link proposed |
| Recipient route | Named access for Luis and Mina | Confirm applicable account controls; actual recipient and signed-out checks pending |
| Supplier request for the recording | No outside access approved | Withhold originals; ask the owner whether a separate sanitized explanation is needed |
| Link duration | Owner proposes access through November 10, 2026 | Approval and configuration remain pending; not a deletion instruction |
| Working archive | Approved internal repository holds the evidence and text | Check actual downloaded files, their completeness, and repository access before treating them as a backup |
| Issue status | Workflow rule unresolved | Keep that status in the message and archive index; a viewed link does not close the issue |
Zight's admin checklist distinguishes organization-only access, named recipients, and anyone holding a link and passcode. It warns that organization-only may still be too broad and that changing defaults does not secure previously shared files. A password should not be described as identifying the viewer. Match the setting to the allowed audience and verify the actual result. Workspace privacy checklist.
The three-seat illustration is $36 monthly equivalent with annual billing, charged as the displayed $432 annual total. Twelve unchanged monthly payments of $45 would total $540, a $108 difference. That comparison excludes unverified taxes, add-ons, and renewal changes. Their recorded recommendation is a controlled Collaborate evaluation focused on named-recipient delivery and archive retrieval, not approval to purchase or upload work files.
Keep sharing defaults, expiration, and retention distinct
If the team later needs different department defaults, inspect the Scale group feature carefully. Its help guide says group defaults apply to new files and can be overridden by members; direct sharing with a group is still described as coming soon. A group default is not proof of an enforced item-level access restriction. Groups guide.
The retention guide describes workspace-wide file policies and post-retention actions, including moving content to trash or deleting it. Do not change a whole workspace merely to make one support link temporary. The fictional November 10 proposal above concerns access to the item; the organization's approved retention and backup rules remain separate. Retention guide.
Zight documents individual and bulk downloads, but the presence of a download option does not prove that Rhea's approved archive contains the expected evidence. During an authorized export check, open S1, S2, and V1 separately, compare their key states with the source, and confirm that the written question is stored alongside them. This article does not attest to export formats, resolution, or preserved annotations from an actual download. Download guide.
Finally, the work explanation must remain usable without assuming everyone can watch a video immediately. Include the written question and meaningful still-image context, and review any captions or transcript before relying on them. Review accessibility needs separately, and keep the request open until the recipient answers rather than relying on a viewer notification.
Buy the delivery capability you can verify
Zight's appeal is a combined capture-and-sharing workflow. Its value for this team depends on a more specific outcome: the right reviewers receive a clear account of the problem, restricted content stays within its intended audience, and the approved archive can be reopened later. Rhea's packet supplies the explanation; the product's actual delivery still needs testing.
Before committing, record the actual account history limit, a named-recipient and signed-out access check, and an opened backup of harmless test material. For other work-tool decisions, return to LandOffer.ai with the same completed evidence packet and explicit open questions. More recording time or a convenient link should answer a demonstrated requirement, rather than substitute for it.



