User Management

Adding and managing users is perhaps the most critical component of the administrator’s functionality group. User management allows for the creation of the organizational hierarchy within the portal, outward reporting visibility, stakeholder controls, and more.

The platform supports three user types in order to accommodate the needs of diverse teams. Administrator users have control of the data ecosystem, can manipulate permissions, settings, or configurations, and manage other Users in the organization. Standard Users are traditionally field operatives who may have some control over certain assets, and whose access to data is slightly more restricted. Anonymous Users can be configured for the purpose of providing public information to interested parties outside of the organization, as with embedded public data on a website, or for family members of tracked personnel.

User Profiles and Configuration

User Profile: Administrator

This is the first User type to be created within an account, as this User type has full control of all facets of the platform account. The Administrator User type should be given only to users with an advanced understanding of the platform, including what they can do with their permission level. Administrators have the ability to control and modify the other User levels, including permissions, assets, settings, preferences, and all other configurable aspects of the platform. The Administrator User type is what you would provide to a dispatcher for a fleet management operation, perhaps a high-level engineer for asset management, or a central command officer for remote ground personnel operations. Understanding the power this user type has is important to the security of the data within your ecosystem, and is recommended that only a small population of the platform users are Administrators.

User Profile: Standard

The Standard User type will be the most common within your organization, and is the most flexible type, allowing for full control of each individual’s permissions, capabilities, and usage. The Standard User permissions can be restricted in such a way that it is quite clear to them the functions and roles of their involvement with the ecosystem and activity within the platform. Access to Assets, Places, Geofences, Alerts, and other aspects of the portal can be configured by the Administrator to be as open or restricted as desired with this User type.

This User type is ideal for field operatives, drivers, fisherman, or anyone in possession of a tracking device reporting back to a central hub. It can also be configured to cater to a team leader, who is responsible for a number of assets or personnel in a given location or operation. This user has the ability to manage that team or Asset Group from an internet-enabled device that can access the portal, and Administrators above that user can monitor multiple sets of Users like this, creating a chain of hierarchy.

User Profile: Anonymous

While this user type is not allowed to login to the portal, this User type gives organizations the ability to make portal data (like the location and behavior of an Asset or Asset Group) available to people outside of the organization through a link. The information can also be embedded on a website, for example, to track a race or other kind of travel activity of a person or group of people participating in an event. For private couriers, this can also be used as a form of tracking a shipment as long as the courier has a tracking device with them reporting location data.

Flexibility of User Types

Because permissions are customizable at any level, system administrators can essentially create subsets of the 3 primary levels that have certain defined permission sets, lending to the creation of multiple levels of Administrators, Standard Users, and Anonymous Users within an organization. This extrapolation of the hierarchy can be beneficial for organizations that need to be able to create super-admins, admins, sub-admins, team leads, and other mid-hierarchy roles within the platform. Organizing the permissions offline and then creating the user profiles with those presets will allow for the development of a system of accountability that is as flexible as an organization is complex.


Permission controls at the User level are handled with check boxes in the Permissions Tab of the Create/Edit User page. They can be configured at any time at the individual User level, allowing managers the ability to grant and revoke permissions on a daily, weekly, or even hourly basis. Permissions include: Add/Edit/Delete for each of the following objects:

  • Assets
  • Asset Groups
  • Geofences
  • Places
  • Journeys
  • Shared Views
  • Send commands to Assets
  • View/Run Reports
  • Change Password
  • Edit preferences
  • Register new mobile device

Managing Users

The following information will be utilized for the creation and management of Users:

  • First name: User’s first name
  • Last name: User’s last name
  • Username: this will be used for login purposes, most usernames are the User’s email address
  • Email address: User’s email address
  • Password: give the User a password that they can change after their first login
  • Confirm Password: re-enter the password to ensure proper spelling and characters
  • Two-factor authentication: set up by default or allow Users to set it up themselves
  • Type: refer to user profiles above for User types (administrator, standard, anonymous)
  • Preferences: these will populate platform defaults, configurable in the Config module, but can be changed at the User level to accommodate needs of diverse organizations
  • Permissions: defaults to a subset of permissions for each User type, but can be customized to create flexibility in User types, allowing for more complex hierarchies
  • Assets and Groups: assign Assets or Asset Groups to the User so that they can see and interact with them
  • Geofences: assign Geofences to the User so that they can see and interact with them
  • Places: assign Places to the User so that they can see and interact with them
  • Contacts: assign Contacts to the User so that they can see and interact with them
  • Drivers: assign Drivers to the User so that they can see and interact with them