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
  • Managing child teams
  • Accessing child teams
  • Configuring child teams
  • Child team ownership
  1. Giraffe Cloud
  2. Reseller teams

Team management

PreviousReseller teamsNextTroubleshooting

Last updated 4 months ago

Managing child teams is slightly different to managing normal teams that you are the direct owner of.

Managing child teams

Child teams are managed from the Reseller button in the main menu.

You can view a list of all your child teams, create new child teams and archive / unarchive child teams.

Archiving child teams is useful for teams that you no longer interested in. Teams cannot be deleted because they may still contain data that the customer needs access to, even after they no longer have access to the hired security equipment.

Accessing child teams

To switch to a child team, you do not use the normal team switch dropdown in the top right hand corner. Instead, you browse to the list of child teams and press Switch Team.

When you switch to a child team, you will see a banner similar to this at the top of your screen:

You can switch back to the parent team quickly using the return to reseller button in the banner. You can also switch to a different team you are a member of using the normal dropdown directly from a child team.

Configuring child teams

Once created, child teams work exactly the same as normal teams. You can proceed to add users, create sites and add devices.

Child team ownership

All teams have to have an owner. When you create a child team, the owner of the child team is set to the same as the owner of the parent team.

We recommend you set the owner of the parent team to be a generic account (such as admin@yourcompany.com) and set it with a long password and 2 factor authentication.

This way, the users on a child team will just see the owner of their accounts as admin@yourcompany.com.

It is technically possible for the owner of a child team to be differet to the owner of a parent team. The main difference this will cause is that the billing will now be linked to the new owner.

In this way, it is possible to have multiple billing accounts with Giraffe for a single reseller team, or for Giraffe to bill one of your customers directly if required.