First establish which task you mean: record what you are watching now, retrieve an earlier event from a card, or keep an event from cloud history. These are different workflows. A Record control in live view does not, by itself, document how to export an existing card or cloud recording.
Choose the guide matching your model and app. This checklist organizes the saving task; the app-specific pages separate documented guide behavior from the steps still needing confirmation.
Identify the source before pressing a control
| Your task | Establish first |
|---|---|
| Save something happening in live view | Whether the matched app/version has a manual recording control and where the resulting file is saved |
| Keep an earlier card recording | Whether the event exists on the card and whether the matched version can export that recording |
| Keep an earlier cloud event | Whether it is still available, which account/plan can retrieve it, and the actual export method |
| Keep a screenshot | Whether you want a still image or the full video; a screenshot is not a video backup |
A notification may help you locate an event, but is not itself proof that a playable recording exists. Write down the event date and the storage source you are checking. If card recognition or compatibility is unclear, use the card-by-model reference before treating an export failure as a card-formatting task.
Use the correct app branch
- O-kam Pro reference: for V8 in Blue or Green and V10.
- Vico Nature reference: separate V9 and V11 notes, including the documented live-view Record use in those editions.
- Other or unmatched app: use the app actually supplied for your unit; do not switch apps to fit one of these references.
The branches do not establish current AI, cloud or sharing rights. The service reference keeps those questions separate.
Verify the result outside the event list
After using a confirmed saving method, locate the result in the destination stated by that app/version. Open the file from that destination, rather than reopening the event in its original history list.
Check that it is the intended visit, that it plays, and that its duration and visible content are what you expected. If sound matters, check it as well. A still image, thumbnail or share link is not the same result as a downloaded video file.
Record the actual destination in the clip-saving worksheet. If you cannot identify a file or the playback still depends on the original cloud/card view, treat the independent copy as unverified. Do not format, erase or remove the source merely to test whether the copy exists.
Check the copy you intend to send
Keep the verified original copy where you can find it. If you make an edited version for a message or social post, label that derivative honestly; a crop or compressed upload is not evidence of the original recording quality. Review the intended clip for household conversations, neighboring spaces and details you do not need to share.
Send only the version you mean to send, through the destination you choose. A recipient receiving a file is different from being invited to the camera. This guide does not send either one. Do not assume that a camera-access change can recall an independent file someone has already received.
If a family member is saving the clip
Choose the result your family member needs
| Intended result | Appropriate question | Do not confuse it with |
|---|---|---|
| See one favorite visit | Can you provide the intended verified video copy? | Giving ongoing access to the camera |
| Watch the feeder through their own app access | Does the matched app support an invitation, and which role applies? | Passing around the owner's password |
| Find and save an earlier event | Can that invited role access the source and complete the saving method? | Assuming live-view permission includes history or export |
| Help with settings | Which specific settings can the role change, if supported? | Automatically giving billing or account-control rights |
The family-access Support reference separates O-kam Pro, Vico Nature and unmatched apps. The older O-kam references distinguish settings access from viewing; the V9/V11 references describe their own sharing routes and account conditions. They do not establish every current guest permission, number of invitees or removal method.
Review permissions as separate tasks
Use the blank family-access review for one matched device/app combination. Record the owner and invited roles without including passwords, pairing codes or private identifiers in a public document. Check live view, history, saving a file, settings and billing separately; a hidden or visible button alone is not proof that the whole task is permitted or completed.
The FTC's camera guidance recommends considering separate permission levels when sharing a livestream and notes that cameras differ. It is general guidance, not proof that a particular Nafnti app offers a named role, schedule or security feature.
Do not pass an owner's password around to work around a missing guest permission. If the role or button differs from the guide, record that difference and ask support for the applicable workflow. If ongoing access is not needed, a deliberately chosen video copy may be the simpler task; its recipient should still understand what they are receiving.
Include how access ends in the plan
Before relying on an invitation, identify the matched method for reviewing and ending that access. Invitation expiry and revocation of an accepted invitation are different events. An old QR-code validity period does not establish when an accepted guest loses access.
When an authorized owner later uses a confirmed revocation method, verify the intended result from both roles under the documented conditions, including a fresh access attempt where appropriate. Record what was actually checked. Do not describe a guest account as removed merely because an invitation screen closed. Revocation of camera access is also separate from copies already exported or sent. This draft does not revoke an invitation, remove a device, reset a camera or transfer ownership.
If saving does not work
Describe the exact stage: finding the event, opening it, starting the documented saving action, locating the result, or opening the resulting file. Include the model/configuration, app and version, phone system, account role and storage source. Keep account credentials and pairing codes out of screenshots or public posts.
For an access question, include the owner/guest role and the specific task that differs. Do not ask a family member to use the owner's credentials or move accounts merely to match an old guide.
For a missing method or an unmatched device, use the app-and-guide checklist and Nafnti contact page. Current button names, destination folders, permissions, quality and plan conditions must be confirmed for that combination; this guide does not invent them.