Giraffe CCTV
  • What is Giraffe?
  • Architecture
  • Giraffe Cloud
    • Getting started
      • Logging in
      • First steps
      • Giraffe terminology
      • Managing your account
    • View and control
      • Live talkdown
      • PTZ presets
      • Quick sounds
      • Custom views
      • Strobes
      • Floodlights
    • Alarm handling
    • Recording
      • Recording configuration
      • Recording playback
      • Exporting footage
    • Schedules
    • Active threat deterrence
      • Arming and disarming
      • Alarm states and configuration
    • System monitoring
      • Overview
      • Graphs
      • Events
      • Error states
    • Notification system
      • Person / vehicle alerts
      • Rate limits
    • Camera setup
      • Artificial intelligence
      • Masking
      • Camera configuration
      • Camera guides
        • Pelco
        • Hanwha
        • Axis
        • Dahua
        • Hikvision
        • Milesight
    • Router integration
      • Peplink
      • Teltonika
      • Advanced
    • Team management
      • Team hierarchy
      • Inviting users
      • Permissions
    • ARC integration
      • Sentinel Native
      • Generic Integration
      • Immix
      • Sentinel - Deprecated
    • Reseller teams
      • Team management
    • Troubleshooting
      • MTU Configuration
    • Advanced
      • Firewall whitelisting
      • White label
    • API
      • RTSP Service
      • HTTP API
  • Mobile App
    • Installing
    • Signing in
    • Live view
    • Recording
    • Updating
    • Privacy policy
  • Edge Controller
    • Edge Controller versions
    • Hardware overview
      • Edge Controller V2
      • Edge Controller V1
        • Status lights
    • Configuration
      • Device definitions
      • Camera power
    • Battery Calibration
    • Mobile routers
      • Router guides
        • Teltonika
          • Unblocking WebUI access
        • Peplink
    • Victron integration
    • SMTP Alarm Receiver
    • PIR sensors
      • Luminite Genesis PIR integration
      • Wired PIR sensors
    • Power consumption
    • Boot / shutdown procedure
    • GPS
    • EFOY integration
    • Advanced
      • Internal queue system
      • Self healing
      • Recording storage
  • Hub Controller
    • Overview
    • Installation
    • Troubleshooting
  • Mobile Security Unit
    • Overview
    • MSU Generations
    • Battery
  • Network Node
    • Overview
  • Mini Tower
    • Overview
    • Transporting the tower
    • Deployment steps
    • On site setup checklist
    • Pack away steps
    • Battery management
    • Solar performance
    • Maintenance
    • Branding
    • Troubleshooting
    • Safety
  • Battery Box
    • Overview
  • Giraffe Battteries
    • Charging
    • Safety
  • Solar Frame
    • Page 1
  • Terms and conditions
Powered by GitBook
On this page
  • User accounts
  • Teams
  • Child teams
  • Sites
  • Edge Controllers
  • Cameras
  1. Giraffe Cloud
  2. Team management

Team hierarchy

PreviousTeam managementNextInviting users

Last updated 1 year ago

The Giraffe Cloud is split into a hierachal structure. The diagram below gives an overview of how it is structure.

User accounts

The top level of the hierarchy are user accounts. A user account can be a member of multiple teams.

A user account can have one of three permissions levels on a team:

  • owner

  • admin

  • member

A team can only have one owner, but it can have multiple admin's and members.

Teams

A team is the top level organisational unit. A team typically maps to a company in real life, but for large organisations, you may split your account up over multiple teams.

A team can have user accounts linked to it who will gain access to the devices on that team.

Child teams

A child team is identical to a normal team, except it is managed by it's parent account.

Any user account that is a member of the parent team, will automaticaly inherit the same permission level on a child team. These users do not have to be manually added to the child team.

The parent team can also see an overview of all the devices on the child team, and has access to various management tools.

Sites

A site maps to a location in real life. Sites are used to organise the devices on a team into groups.

A team can have multiple sites, but a device (normally an Edge Controller) can only be linked to one site at a time.

Edge Controllers

An Edge Controller is linked to a site.

Cameras

Cameras are always linked to an Edge Controller.