Documentation & Setup Guide
A practical companion to the IVISION website, covering camera preparation, detection planning, reports, troubleshooting, and the available product references. This file can be read offline or printed from your browser.
Website resource edition · October 2026. Your installation, permissions, and available features may differ. Ask your IVISION contact for deployment-specific administration and API documentation.
Introduction to IVISION
IVISION presents camera activity as events that teams can review and act on. The public website illustrates the relationship between cameras, monitored areas, detection rules, event activity, and reports.
Start with the environment you want to monitor and the action your team should take when an event occurs. Then identify the relevant cameras, choose the detection scenarios, and plan a limited pilot with representative footage.
Camera setup checklist
Prepare the following before connecting a camera. Connection and commissioning should be completed in your own product environment with the appropriate permissions.
- Choose a useful view. Identify the area, entry point, workstation, or activity you need to monitor. Confirm the view is clear during normal operating hours.
- Record the camera details. Note the camera name, location, model, network address, and the stream details provided by your camera administrator. Keep passwords in your approved secret manager.
- Confirm authorized access. Ask the camera or network administrator which account, stream, and network path your deployment should use.
- Check the network path. Verify that the intended deployment can reach the camera. Review firewall and routing requirements with the network team.
- Confirm the live picture. Check focus, lighting, camera angle, obstructions, and whether important activity remains visible.
- Name the camera clearly. Use a consistent site, floor, and location naming convention so events are easy to identify.
- Plan the first scenario. Choose a specific use case, define the monitored area and schedule, and agree who will review the first events.
- Validate with representative activity. Review both expected events and normal behavior. Record issues and adjust the setup before expanding coverage.
Never paste camera passwords or private stream URLs into public forms or website demos.
Configure detection rules
A useful rule connects a specific observation with an agreed response. Write down the following before configuring your deployment:
- The event or scenario to detect.
- The camera and relevant area in its view.
- The schedule or operating conditions during which the rule should apply.
- The priority of the event and who should review it.
- Examples of expected activity and common false alarms.
Test one change at a time and review the resulting events with the people responsible for the area. The public platform rule builder is an illustrative preview; it does not configure a customer account.
Dashboards and reports
Use a consistent date range, camera selection, and event category when comparing activity. Review individual events before drawing conclusions from totals.
- Confirm the selected site, camera, and reporting period.
- Check whether changes in camera availability or operating hours affect the comparison.
- Review representative events and record the response or follow-up.
- Share only the information needed by the people responsible for the work.
Troubleshooting & FAQs
The camera is not available
Confirm that the camera is powered on, that the intended network path is available, and that the configured stream details and authorized account are current. Ask your administrator to check access without sharing credentials in a support message.
The camera picture is available, but the expected event is missing
Check that the correct scenario, camera, monitored area, and schedule are selected in your deployment. Review lighting, obstructions, and representative footage with your IVISION contact.
There are too many unwanted events
Collect a few representative examples with their timestamps and camera names. Review the camera view, monitored area, operating schedule, and configured scenario before changing detection settings.
A report looks different from the dashboard
Compare the time range, time zone, camera selection, and event categories. Confirm that both views refer to the same period and available cameras.
Does the website demo change my cameras?
No. The public website previews are illustrative and independent of the customer portal.
What should I include in a support request?
Describe what you expected, what happened, the affected camera or site name, the approximate time, and steps already tried. Include only information you are authorized to share, and omit passwords and private stream URLs.
Videos, integrations, and support
- Video library
- Use cases by environment
- Integration overview
- Deployment options
- Platform updates
- Request API documentation
- Contact support
When you need installation-specific commands, API endpoints, or account permissions, request the documentation that matches your deployment from the IVISION team.