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
  1. Giraffe Cloud

Reseller teams

PreviousSentinel - DeprecatedNextTeam management

Last updated 4 months ago

It is possible to setup a parent / child team hierachy. This might be used when you are a security firm, and you rent systems out to customers.

When you get a new customer, you create them a new child team under your main team.

You can then add the customer's staff members to the child team to give them access to the camera. You do not need to add yourself as you will inherit permissions from the parent team.

See the below diagram for an overview of the structure:

Please note that child team hierachys can only be 1 layer deep. Deeply nesting child teams is not supported.

If you believe you require a deeply nested team structure, you are probably not using sites correctly. Sites allow you to subdivide a team.

If you genuinely need nested child teams, you can achieve a similar thing by having multiple 'parent' teams each with it's own child teams.

Benefits of child team hierarchy

The benefits of the above structure are as follows:

  • Each customer is individually 'siloed' and there is no chance of their data being leaked. If you have all your systems in one team, and you accidentally configure the permissions wrong, you risk leaking a customers data to the wrong person.

  • The customer can continue to access their data (such as exported recordings and video events) long after the system has been off hired. They can also retain their user accounts, saving time if they hire another system in the future.

  • The customer can manage their own system if desired. If you have all your devices in a single team, any user you make an admin will have access to all systems in the team.

  • You only have to add your staff members once to the parent team and they can inherit permissions to the child teams.