Skip to main content

Installer Onboarding Introduction

Erik Wihlborg
  • Updated

The Installer Onboarding feature allows Telematics Service Providers (TSPs) to automate installer and user provisioning in the SKF TraX platform using the TraX API. This replaces manual setup with a scalable, API-driven process.

Overall, the feature streamlines installer onboarding, improves time-to-value for fleets, and enables TSPs to scale operations securely and efficiently.

 

 

Key goals

  • Fast onboarding: Fleets can start working immediately after TraX integration, with vehicles visible and device commissioning available right away.
  • Scalability through delegation: TSPs can reduce manual effort by delegating installer onboarding, user management, and device commissioning.

 

Overview

The Installer Onboarding feature extends the TraX API with functionality in the areas of:

  • Initial provisioning: Automatically creates installer companies, initial users, and access rules to fleet resources.
  • Ongoing administration: Supports adding additional installers and users, and managing access over time.

Previously, installer setup and access management were manual and slow. New TraX Partner API capabilities now enable automation, improving efficiency and security while supporting growth.

 

Background

In the TraX concept model, an installer is the party responsible for installing TraX devices. By default, the TSP is authorized to perform installations, but this responsibility can also be delegated to a fleet owner or a third party (for example, a repair shop).

For a TraX mobile app user to be permitted to install devices, the following requirements must be met:

  • A company representing the user’s real-world organization must exist in the SKF platform.
  • The user must have an account in the SKF platform that is associated with that company.
  • A rule must be in place granting users from that company access to one or more fleets managed by the TSP.

With the new API capabilities, TSPs can reliably and efficiently comply with the TraX installer access requirements outlined above.

 

API Capabilities

Company management

  • Installer companies (fleets or third-party) can be created via API.
  • Companies are globally unique and defined by email domains, which control user creation.
  • Third-party companies are visible by default.
  • Fleet companies are not visible by default for commercial reasons. A fleet company becomes visible to a TSP only after the TSP explicitly creates the company, even if the company already exists in the platform.
  • The TSP’s own company is always visible, allowing the TSP to create users through the API in the same way as for other installer companies.

 

User management

  • Users can be created only if their email matches the company’s registered domains.
  • Users with free email domains must be created using the SKF platform.

 

Access control

  • Access rules grant all users in a company access to specific fleets.
  • Existing users gain access within seconds; newly added users may take up to two hours.

 

Implementation Resources

 

Related articles

Comments

0 comments

Article is closed for comments.