The ezeio system is designed to allow a user (potentially) to have access to multiple groups and/or accounts from a single login. Registering your first ezeio creates your account. Additional groups and sub-accounts can be created to organize ezeio controllers, dashboards, users, services and more.

A “group” in the ezeio system works just like a folder on your computer. Groups are arranged in a tree-structure, where each group may contain other groups, on its branch. There is no limit to how many groups you can create, or how many groups can be contained in a higher-level group.

In addition to containing other groups, each group may also contain ezeio controllers and users. There is no restriction on how many ezeio controllers a group may hold, if any. This is similar to how you can store files in folders on your computer (the files being ezeio units and users, while the folders are comparable to groups).

A group is not required to contain an ezeio. You may choose to use a group to manage user access to it's subgroups. For example: a chain of stores may have regional management and maintenance personal without a physical office or need for an ezeio. In this case, their access and privileges' would extend to the subgroups below, that contain the ezeios in the individual stores.

A single ezeio controller can only be located in a single group, although it's data and some controls can be linked to dashboards widgets in groups higher up the branch of the group tree.

You may use the group structure to manage your controllers in any way that makes sense for your organization. If you only have a small number of ezeio's it may be sufficient to just have a single group, but as you add units you probably want to organize them in groups by location, client or function.

Accounts are specially designated groups that isolate branches of group tree. The “Root level Account” separates your parent organization from all others on eze.io, like a bank account. Sub-accounts create divisions within your account, like checking, savings, and the kids collage fund. This allows account level services such as SMS messages, voice messages and API calls to be purchased and consumed by a selected group or branch. Where as groups provide organizational structure, accounts add security, privacy and exclusivity. If your organization/company provides products or services to other organizations sub-accounts allow you access to your clients, without allowing them access to each other.

Root level Account

A root level Account is automatically created by clicking the “Don't have an account? Sign up here” link. This process requires the serial number and registration code of an unregistered ezeio and email address not associated with a user. Most account holders on eze.io will only need to do this once, as additional controllers, users, groups and sub-accounts are added from within. The root account cannot be deleted.

Sub-accounts

Any group can be promoted to an account, making it a sub-account of the root account or of another sub account. Users with the required privileges can “Right-Click” on a group and select “Make account” to start the promotion process. You will then be asked to enter the billing information for this account. After submitting the billing info, you are instructed to logout (and back in) for the changes to be visible. Click on the new account and view the Account settings under the “Group settings” tab. At the bottom you will see check boxes for allowing credit card or invoice payment. If these are left unchecked users invited to this account will not have the ability to purchase services or view pricing.

Separating account level services and destinations

Message credits (text and voice) and API calls are “Account level services”. This means, if you only have one account these services can be consumed by any group or ezeio. Creating sub-accounts allows services to be restricted to a specific branch.

Destinations and Destination lists are also accessible account wide. These are the contacts (end points) and groups of contacts for alarms messages within an account. These destinations can contain sensitive personal information such as cell phone numbers. At a minimum the “Destination lists” may be irrelevant to other groups in an account or lead to alarm messages sent to the wrong recipients.