First decide whether the other person needs one video or ongoing access to the feeder. Sending a deliberately chosen video copy and inviting an account to a camera are different tasks. Match the current app, hardware and owner/guest roles before using sharing instructions.
Choose the intended sharing task
| Intended task | What needs confirmation |
|---|---|
| Send one bird visit | A verified file and the version/content you intend to share |
| Let someone watch through their own account | A supported invitation method and the actual viewing role |
| Let a family member find or save recordings | Their access to that storage source and the supported export action |
| Let someone help with settings | Which settings that role may change, with an authorized scope |
| End ongoing access | A matched revocation method and a way to verify its effect |
Do not pass the owner's password or pairing code around as a workaround. Use Save and verify a bird visit when a selected file is the intended result. No invitation or message is sent by this draft.
Match the model and historical app reference
The following table identifies the archived branches. It does not assert that every current unit uses one of these apps or that the old invitation limits still apply.
| Feeder | App & Wi-Fi | Guide note |
|---|---|---|
| V11 | VicoNature · 2.4 GHz only | Use the instructions supplied with your feeder for hardware-specific steps. |
| V9 | VicoNature · 2.4 GHz only | Use the instructions supplied with your feeder for hardware-specific steps. |
| V8 · Blue or Green | O-kam Pro · 2.4 GHz + 5 GHz | Use the instructions supplied with your feeder for hardware-specific steps. |
| V10 | O-kam Pro · 2.4 GHz + 5 GHz | Use the instructions supplied with your feeder for hardware-specific steps. |
| V5 | VicoNature · 2.4 GHz only | Use the instructions supplied with your feeder for hardware-specific steps. |
| V7 | VicoNature · 2.4 GHz only | Use the instructions supplied with your feeder for hardware-specific steps. |
| Adjustable Camera Feeder | VicoNature · 2.4 GHz only | Use the instructions supplied with your feeder for hardware-specific steps. |
An arrow in this table is a historical reference, not an instruction to tap those controls on an unmatched unit. Older guides describe invitation conditions, including code/account or region conditions in particular editions. Invitation validity, accepted access and the number of simultaneous viewers are separate questions; no old number is promoted to a current limit here.
For another app or an uncertain match, preserve the actual supplied app/publisher/version and use Find the app and guide. Multiple apps coexist; do not migrate an account to fit a historical tutorial.
Review the invited role task by task
Use the blank family-access review for one device/app/role combination. Define the intended scope before an invitation; use actual observations when a properly authorized, matched review is later performed.
| Permission/task | Evidence to record | Separate question |
|---|---|---|
| Live view | The invited role's actual supported viewing result | Access to earlier events |
| Card/cloud history | Which source and event the role can open | Exporting that event |
| Saving a file | The documented action and verified file destination | Permission to change settings |
| Settings | The specific allowed task, not just a visible menu | Billing and subscription control |
| AI/cloud entitlement | The benefit actually available to that role | The owner's entitlement applying to everyone |
The FTC's camera-sharing guidance distinguishes possible permission levels and notes that products differ. It does not certify a specific Nafnti role, encryption feature or invitation flow.
A visible label, a closed dialog or an invitation sent successfully is not a completed permission review. Record “not checked” when there is no evidence, and do not test by changing a plan, deleting clips or granting broader access than intended.
Keep O-kam Pro, Vico Nature and other apps separate
The older O-kam Pro examples distinguish an option affecting settings permission from viewing-only access. That distinction does not establish every current guest's ability to browse history, export, identify birds or subscribe. Use the O-kam saving reference for its existing evidence boundaries.
V9 and V11 Vico Nature references each describe their own owner/invited-account route. Their documented live-view Record use is not proof that an invited account can download an earlier card or cloud event. Use the Vico Nature saving reference and keep the hardware editions separate.
For another app, keep the unmatched branch. Region/account requirements, invitation acceptance, current role behavior and removal steps need actual matching. A failed invitation should be recorded with its message and stage, rather than answered by changing regions, sharing credentials, rebinding or resetting.
Plan and verify how ongoing access ends
Before relying on sharing, establish where the authorized owner reviews accepted access and which matched operation ends the intended access. Code expiry is not the same as removing a person who has already accepted. Logging out, closing an app and unbinding a device are also different actions; do not substitute one for a documented revocation method.
The material reviewed for this draft does not establish a complete current revocation sequence for every model/app. When a matched method is later confirmed and an authorized owner uses it, verify the result from both roles under its documented conditions. Record what was actually checked and keep a failed or incomplete result open. Do not claim that an accepted invitation was revoked merely because the invitation page disappeared.
Keep cloud/card access, account ownership, billing and independent exported files separate. Do not assume a camera-access change recalls a file already received by another person. This draft contains no deletion, ownership transfer or revocation operation.
Prepare the intended clip or a focused support question
For a file, check the actual saved version before sending it: correct visit, playable content and no unnecessary private surroundings or conversations. Keep an edited social copy distinguishable from the original. The placement guide covers the intended frame; reviewing a final clip does not establish the scope of an unverified privacy-mask feature.
For an access problem, record the exact configuration/batch, current app/publisher/version, owner or invited role, intended task, message and the stage that failed. Keep passwords, codes, account identifiers and home details out of public examples. Ask for the matched task or revocation method rather than requesting a universal shared-account workaround.