ezeio2:mange:groupsettings

Group Settings (account, group, user management)

Overview

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.

Groups can be moved within an account, where as the root level account is fixed. Since users and dashboards belong to the group/account), relocating the configuration from a root level account would require, recreating dashboards and inviting users to the new group. For this reason we strongly recommend creating at least one group below your account to set-up your ezeio controllers.

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.

If using an existing user's email to generate a new account, the system assumes you are a using the wrong process to add an ezeio to an existing account and redirects you to the sign in.

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.

To access the ezeio system, you need to have a user login. The user login consist of you email address and a passcode of your choice. Please choose a strong passcode, using at a minimum eight characters, and not comprised of common words that can be easily guessed. Use a mix of lowercase and uppercase letters and numbers/special characters in your passcode for better security.

The ezeio system does not store your actual passcode. There is no way to find out what your passcode is in case you forget it. The system provides a way to reset your passcode by sending an email to your registered email address. Please use best practices when you select and keep your passcode.

Every individual that uses the ezeio system should have a personal login. Never share passwords with others. Do not use shared email addresses. If you do not have an email address, there are many free services such as Gmail, Outlook or Mail.com where you can create a personal email address for use in our system.

Each user is associated with one or more groups. By default, users will have access to all lower-level groups contained within the users' highest level group, but the administrator can override this (see Privileges).

To add more users to a group, simply navigate to the Group Settings screen and click Invite user (see Registration for complete instructions). A user can be invited to groups within multiple organizations/accounts.

The first user to register a controller for your organization will automatically receive all privileges. This will also automatically create a group and mark this group as the “Account”. Account groups are shows in bold in the group tree, and cannot be deleted or moved the same way a normal group can. Also, the Account must always have a user associated with it, which happens automatically when the account group is created.

Under the Group Settings tab are three windows, Manage Group and Account, Manage Users, and Manage API keys. The Manage Group and Account window is open by default when selecting the Group Settings tab. The other windows are accessed by clicking their banners at the bottom of the window.

Users with “Can edit group” and “Can edit payment method” can view and make changes to the following;

  • Group name (name can be included in alarm messages using the Message template tag [GROUP])
  • Group notes (enter text to inform other users about group specific details)
  • Account billing contact (editable through account, grey'd out in groups)
  • Select credit card and/or invoice billing
  • Billing day (select the day of the month you wish to receive invoices)

Users with adequate privileges can perform the following tasks

  • Invite users
  • Delete users
  • Edit users
  • Add or remove user privileges

This window is for creating API keys. Users with “Can access API keys” can create new API keys by Left-Clicking on the “+” symbol at the upper right of the window. The new key's will have a default name, expiration, key ID and key. Make the desired changes to the settings listed below and click submit. The new key and ID can be used in API calls to eze.io servers. See API reference for details.

  • API key name - This name is for key management reference only, it is not used within the code of an API call.
  • Privileges - Options listed correspond to the available API calls. Select any number of privileges per key.
  • Key expires - This date is typically set far into the future, but can be used for temporary calls or testing. The default setting is 1 year.
  • Inherit to subgroups -
  • Call back URL -
  • Key ID - Auto generated, cannot be changed
  • Key - Auto generated, cannot be changed
  • ezeio2/mange/groupsettings.txt
  • Last modified: 2021-02-18 00:12
  • by johpar