View Categories

Users

Users page allows server managers to view users, camera usage, storage usage, and account status.


Users: Displays all users with key details including email, status, storage usage, camera usage, and created date, along with available actions for management

Add User: Allows you to create a new user by entering required details such as name, email and password and automatically assigns initial access and permissions.


users


User Roles and Permissions

Camlocus uses three main user roles:

  • Admin
  • Manager
  • User

Each role has different access rights. Access is based on resource ownership and explicit sharing. A user does not automatically see cameras, locations, alerts or playback from another account unless those resources are shared or assigned.


Admin

Admin is used for system and server-level management.
Admin can:

  • manage server/global settings
  • create Managers
  • manage account limits
  • access administration pages
  • view usage and system information

Admin should not automatically view customer or Manager private video content in Live Stream, Alerts or Playback by default.


Manager

Manager is used for customer/account-level management.

Manager can:

  • create cameras
  • create locations
  • create Users
  • manage cameras and locations created by that Manager
  • share own cameras with Users or other emails

Manager cannot:

  • see Admin cameras by default
  • edit/delete Admin-created cameras shared with him
  • see other Managers’ cameras
  • access server/global administration settings


User

User is a viewer-level account.

User can:

  • view cameras assigned/shared to him
  • access allowed live stream, alerts and playback

User cannot:

  • create cameras
  • create locations
  • create users
  • edit/delete cameras
  • access server/admin settings


Main permission rule

Owner can manage.
Shared user can view/use only.

A Manager can access:

  1. resources created by that Manager
  2. resources explicitly assigned/shared to that Manager

A Manager should not automatically inherit parent Admin resources.