Answers to Common Questions

There are several common questions that we get as people start using the Eagle Eye Networks API.

Why is my list of devices empty?

The list of devices returned depends on the permissions that the user has. It will only return items that they have access to. This can include devices in the same account or devices shared with them from another account.

If you user is created on a reseller account you will not have access to any devices until you switch into a sub-account. The reseller account itself does not contain any devices. All devices live in sub-accounts. You can get a list of sub-accounts and switch context into any account you have access to. After changing your context, you will have access to the devices in that account with administrator permissions.

Why are there two different places to add users?

The reason we have users in both places is so you can add users to just a specific sub-account or have users that work for the reseller that can manage multiple sub-accounts.

Imaging having two different installations, not having a reseller account make it difficult to manage all equipment and users in a single account. It would also be challenging to make sure every user had the correct permissions to just their equipment.

By separating out the reseller and the sub-accounts, we can provide isolation so that cameras are not inadvertently shared. We can also provide a much simpler user management interface.

Verify the user has permission to access devices

We want users to be in control of their devices. Each user can be given access to all, some, or none of the devices in an account. The account administrator configures each user with both the device and the specific permissions granted for the device.

I recommend following the guideline of least permission. Each user should be given enough access and permission to complete their job but should not be given any unneeded access or permission.

Following the above guideline is a good security practice because it limits the potential changes a user could make by mistake. It also limits the overall damage that could be caused if a user's credentials were compromissed.

What else can we do with this?

The options are almost limitless. It really just depends on what you wanting to do. Please feel free to reach out to me directly at mcotton@een.com