Quick answer: Give each person or integration an identifiable account and only the permissions needed for its job, where the device supports that arrangement. Agree who controls administrator access and test the actual restrictions before handover. Do not use one shared installer login as the customer’s access plan.
On this page
Agree account ownership before commissioning
The customer needs an authorized administrator and a recovery arrangement that does not depend on an employee who may leave. The installer may need separate service access under an agreement. Settle those responsibilities in writing instead of leaving the only administrator password with whoever happened to commission the recorder.
Protect credentials through the approved password-management process. Record who holds access, not the passwords themselves, in the handover document. Remove temporary commissioning accounts when they are no longer needed.
| Person/system | Required tasks to test |
|---|---|
| Customer administrator | Account administration and approved configuration/recovery tasks. |
| Day-to-day operator | Only the required live view, playback and export functions. |
| Restricted viewer | Only approved channels/functions; test both allowed and denied access. |
| Installer service account | Authorized maintenance functions, review/expiry and revocation path. |
| Third-party integration | Only supported device/channel/service access needed by that integration. |
Use the permissions the actual model offers
Administrator, operator and viewer are useful functional descriptions, not guaranteed menu names or identical role sets across every CASE NVR. Check channel restrictions, playback/export rights and configuration controls on the exact model and firmware.
Write down what each role must do and must not do. If the product cannot enforce a required boundary, resolve the design rather than promising the restriction from a generic checkbox list. A successful administrator test says nothing about a limited user’s experience.
Test allowed and denied actions
- Sign in as the intended user on each in-scope interface.
- Test approved channels, live view, playback and export separately.
- Try the actions and channels that should be unavailable.
- Check whether the account can change recording, network, users or other protected settings.
- Record the result and any difference between local, browser, app or desktop access.
Do not assume permissions transfer unchanged from a recorder account to a remote service or mobile sharing arrangement. Confirm CASE Connect’s supported ownership, sharing and removal behavior for the actual device and app version; see CASE Connect handover.
Give integrations their own identity
A VMS, decoder or other integration should use a separate appropriately limited account where supported. Match its permissions to the actual connection and functions. Verify the exact devices, firmware, ONVIF profile and required behavior rather than claiming universal compatibility.
Name and document the integration account so another technician can identify it. Do not silently reuse the administrator login because a third-party platform is easier to configure that way. Check the official conformance record where conformance is required, then test the real combination.
Prove that temporary access can be removed
Agree a safe test window and use a temporary authorized account. Verify customer administrator access first. Confirm which local and remote routes work, then revoke the test access through the supported controls.
Attempt those routes again, including a new sign-in and relevant existing sessions. A local-user deletion may not remove a separately shared app account or service token. Record what was actually blocked, any residual session behavior and the procedure needed to complete removal.
Never disable a live operational account without authorization and an impact/recovery plan. Keep the customer’s required access available throughout the test.
Keep the access list useful after handover
Record names/purpose, approved role/functions, channels, interfaces, owner, review date and revocation method. Store the list with restricted access and no secrets. Review it when staff, tenants, service providers or integrations change.
Check the logs the device actually provides for relevant access and changes. Do not promise that every action is audited or that a named account makes a log a complete legal record. Time and log configuration are covered in time, logs and certificates.
Use the hardening baseline with the customer handover form. Both the customer and installer should know what maintenance access remains.
FAQ
Should the installer keep administrator access?
Only through the agreed authorized arrangement. A separate supported service account is preferable to sharing the customer’s routine identity.
Can a viewer always be limited by channel?
Confirm that function and its behavior on every relevant interface for the exact model/version.
Does removing a recorder account remove every remote session?
Do not assume it. Test the confirmed local and remote paths and follow the service’s removal process.
Send the required permission matrix, full SKUs and versions to Anabon technical support before promising a multi-user or multi-tenant arrangement.
