The Manage module contains all of the editing and control functionality for non-map-view features, and consolidates many of the tools that allow portal users to enhance their Asset ecosystem.
Users can create or manage their existing Alerts from this interface. When managing Alerts, users will see the name of each Alert, along with its trigger condition, Assets and Groups to which it applies, any filters that apply to it, contacts and the type of notifications each receives, and any Assets for which it is currently triggered (if applicable). Users will also have the option to Edit and Delete each Alert directly from the list by clicking the Green button (edit) or the red button (delete) on the corresponding line.
Users can create or manage their existing Contacts from this interface. When managing Contacts, users will see the name of each Contact, along with the Destination (associated phone number or email). There are also indicators for whether the Contact is set up as an Emergency Contact, and for whether or not the Contact is active for the User. For each Contact, a button will appear inline that will allow Users to send a test message to that contact to verify the accuracy of the information and the portal’s ability to deliver to that Destination. Users will also have the option to Edit and Delete each Contact directly from the list by clicking the Green button (edit) or the red button (delete) on the corresponding line.
Users can create or manage existing Journeys from this interface. When managing Journeys, users will see the name of each Journey, as well as the list of Assets included, number of Trips, begin and end dates, and whether or not the Journey is enabled (can be viewed in the Journeys module).
Users will also have the option to Edit and Delete each Journey directly from the list by clicking the Green button (edit) or the red button (delete) on the corresponding line.
Users can create or manage existing Shared Views from this interface. When managing Shared Views, users will see the name of each Shared View, as well as the expiration date, viewing restrictions (public or private), and whether or not the Shared View is enabled (if the link is active). Additionally, the platform tracks the activity of Shared Views, including the creation and edit dates, which are also displayed in the list.
Because Shared Views provide external parties with access to view data on a map interface, the portal tracks this viewing activity and those activity reports can be found in the Statistics button (pie chart) under operations for each Shared View. Other quick button operations include viewing the Shared View as it would be seen by the public (eyeball button). Copying the Shared View link to the clipboard (link button), and Sharing the Shared View link directly from the portal to social media and email.
Users will also have the option to Edit and Delete each Shared View directly from the list by clicking the Green button (edit) or the red button (delete) on the corresponding line.
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.
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
- Preferences: These will populate platform defaults, configurable in the admin panel, but can be changed at the user level to accommodate the 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
Address Books have no properties within the portal except for their name. They are container elements for Address Book Entries, which are device-specific versions of Contacts. Use this option to create or edit address books.
Address Book Entries
Address Book Entries are device-specific versions of Contacts. Add or edit individual entries for address books.
Canned Message Groups
Canned Message Groups have no properties within the portal except for their name. They are container elements for Canned Messages, which are device-specific versions of Quick Messages and Templates. Use these to sort your Canned Messages.
Canned Messages are device-specific versions of Quick Messages and Temaplates. Use these as auto-responders, message templates, or common status updates to save time.
Manage vessel operator data, including login credentials and personal information.
- First name: Driver first name
- Last name: Driver last name
- Username: Driver username for login
- Password: Driver password for login
- Duress Password: To be entered to alert managers of dangerous situation, such as hijacking
- iButton ID: Identification number printed on the iButton ID, if using iButton logins. Some devices require a 12 byte ID (not including the checksum) and others require the entire 16 byte ID. Check with the specific manufacturer to confirm which is required.
- Phone Number: Driver phone number
- Blood Type: Driver blood type (in case of emergency/unconscious)
- License Number: Driver’s license number
- License Expiration: Driver’s license expiration date
- License Restriction: Driver’s license restriction code(s), ie: Glasses, night
- Manager: Driver’s manager
- Emergency Contact: Driver’s emergency contact name
- Emergency Contact Number: Driver’s emergency contact phone number
- Photo: Of the Driver or documentation such as licenses
Driver Status Templates
Use this to create simple options for Drivers to choose from the interface on their reporting devices. The most common status template options are active, off duty, resting, delayed, delivering, waylaid, and in distress
Manage gateway accounts, which have special permission levels.
Use this to create the fields to be used with Garmin devices for Driver reports.
I/O Mapping Templates
Use this to configure the layer of sensors and third party tools feeding into the reporting device.
Use this to add or change permissions for each available map layer. Currently available by default:
- US Weather Radar
- AUS Weather Radar
- World Satellite Infrared
- Weather Forecast
- Iridium Satellites
- Iridium NEXT Satellites
- Inmarsat Satellites
- Globalstar Satellites
- Orbcomm Satellites
- Comm. Satellites Administrators can also add custom map layers to the platform from this option, and make them available for all users.
Quick Message From-Mobile Templates
Similar to canned messages, use this to set default content for quick messages
Quick Message To-Mobile Templates
Similar to canned messages, use this to set default content for quick messages.
User Email Templates
Use this to pre-populate content for an email, leaving only form information to fill in.