IO Frog 2.0

Here you will find all specific features related to IO Frog 2.0. The key changes:

Devices are organized in groups
1. All groups are in one tree-like structure
2. User can create own sub-groups
Users have specific access to groups. The access is defined by user permissions and roles.
Categories are transferred into Tags
Microservices are now Forwardings with the improved user interface
Tag, Geoplaces, Rules, Public Channels, and Forwardings (formally Microservices) are moved from user level to group level and thus are available for all devices in a group.
New Notification rules
1. Multiple recipients
2. Message templates
3. You identify recipients of push notifications by their e-mail (multiple allowed) so, only these users will receive push notifications.
4. Conditions using boolean AND/OR logic and all data from the message
5. Because notification rules are now defined on group level, there are no notification settings on device level (it applies to web and mobile apps). Because notifications are now more complex, you have to manage them in web app only.
Invitation of new users to the selected group
Updated API documentation in standard Open API 3.0 format

Groups

All devices are organized inside groups. One device may belong to one group only. The purpose of groups is to:

Organize all devices in a tree-like structure primarily based on the ownership.
Define all features once on the group level and apply them to all devices in the group.

Groups are accessible right from the top menu where you see the name of the current group. There are 3 sub-menu items under the current group name:

Billing
- Orders,
- Billing data
- Credits
Settings
- Group management
- Management of all group features including Tag, Geoplaces, Notification rules, Forwardings, Public Channels
Change the group – change the current group. Here you will see your own group (if you have one) and all groups you have an access to, e.g. groups you were invited to.

1 2 3 4

There are 2 types of groups

Contract group – the main group that besides devices may also contain: billing data, orders/invoices, credit, and shopping cart. Every contract group must have at least one owner (= user with full ownership rights). You cannot delete the group if there are orders or SMS credit left.
Standard group – you can create any number of groups and sub-groups under contract group for better organization of devices.

Migration of users and devices into the new structure

All users having their own devices will have their own CONTRACT group in IO Frog 2.0.
The CONTRACT group will contain all devices owned by the user
Users will have full rights to the CONTRACT group.
Notification rules, geo-places, and tags (formally categories) are migrated to groups

Limitations of migration process

Users not owning any device will not have their own CONTRACT group after migration. Their accounts will be fully manageable by users with an access to parent group.
Geoplaces, notification rules, billing info, and credits of users not owning any device will not be migrated because they do not have their own group, only an access to somebody’s else group.
Custom body in forwarding definition is not supported, server will forward all data

What to do after migration

Check all tags, geoplaces, notification rules, and public channels
If multiple devices in the group are using same forwarding instructions, you can keep only one forwarding with All devices set to true.

Geo-places

Define geo-places inside in group and monitor devices entering/leaving the geo-place. Application of geo-places is done on 2 levels:

Messages are enriched by Arrival to / Departure from attributes if devices entered/left the specific geo-place
You can set up notification rules using the geo-places and receive notifications in case the device enters/leaves specific geo-place

1 2 3 4

1 2

Notification rules

Notification rules enable you to define rules that will be applied to all or selected devices of specific type inside the group. Notification rules enable to set:

Multiple recipients
E-mail, SMS, Push notifications
Custom template using pre-defined variables
Multiple conditions with AND/OR boolean logic

Public channels

You define all public channels inside a specific group and assign devices to channels on one screen. All devices inside the group can be automatically visible inside the channel or you select the sub-set of devices.

1 2 3 4 5

1 2

User management

Go to Group > Settings
Choose the group
Add a new user
1. Existing users will be assigned = DONE
2. Non-existing users will receive an e-mail with an invitation to join IO Frog. They will be able to complete the signup by clicking on the link in the e-mail.
Optionally change the group type to CONTRACT
1. Changing group to CONTRACT is possible only if there is at least one user in the Owner role
2. CONTRACT group has own shopping cart, billing details, and orders

1 2 3 4 5 6

Permissions

Users have a relation to groups. There are 4 types of rights:

No-access
Read-only
Update
Full management

You can control these rights for every user:

Group management – access to the tree, creating new sub-groups, deleting subgroups, etc.
Access management – management of user access
Device access – read / update / full management of devices
Downlink – update device settings via downlink messages
Connectivity – buy/extend connectivity
Tags – manage tags
Geoplaces – manage geo-places
Notification rules – manage notification rules
Public channel – create channels and publish devices in channels
Forwarding – view/set forwarding to other servers
API calls – access data via API calls
Diagnostic data – access diagnostic dashboard and message log
Sigfox data – access data from Sigfox backend (e.g. PAC code)
Credits – manage SMS credits

EXAMPLE

1) I am signed in as a standard user

2) I can see my own group in the list of groups (first group on the list) but I also see all groups I was invited into (with specific permissions).

3) After I switch to one of such groups, my user interface adjusts to the permissions I have into the selected group:

In this case, the permissions are Read-only.

E.g. no possibility to register a new device

No possibility to update device settings

Or no possibility to delete messages