Skip to content
  • There are no suggestions because the search field is empty.

MyGeotab Integration & Access Requirements

To facilitate carsharing and telemetry services, Launch Mobility requires integration with your MyGeotab environment. Depending on who manages your Geotab database, please follow the relevant section below.

Section 1: For Third-Party Resellers

If you are a Geotab Reseller managing a client's database, please follow these steps to grant Launch Mobility access:

  1. Invite Launch Support: Add a new user with the email telematics@launchmobility.com.

  2. Naming Convention: Once the initial connection is established, Launch Mobility will provision two specialized accounts using the following plain text formats:

    • Portal Account: telematics+[OrgSlug]@launchmobility.com

    • API Account: telematics+[OrgSlug]api@launchmobility.com

  3. Permissions: Both accounts must be set to Administrator level to allow Launch TSEs to monitor Keyless hardware logs and maintain the API data bridge.

  4. Finalize: Click Save in the upper right-hand corner to create the user and trigger the invitation.


Section 2: For Self-Managed Organizations

If you manage your own MyGeotab database internally, please follow this streamlined setup:

  1. Create Initial User: Add telematics@launchmobility.com as a user in your MyGeotab portal with Administrator clearance.

  2. Trigger Invite: Click the Save button in the upper right-hand corner. This automatically creates the user and sends the invitation to the Launch TSE team.

  3. Launch Handover: Our team will access the portal via this initial account and internally configure the required diagnostic and API accounts (using our standardized telematics+[OrgSlug] format) to complete the integration.


Technical Specifications

  • Security: Launch Mobility is SOC 2 Type 2 compliant.

  • Data Residency: All data is hosted on US-based AWS servers.

  • Usage: Launch utilizes Administrator access strictly for monitoring Keyless Monitor logs and diagnostic purposes; we do not modify fleet settings without authorization.