Connecting to Wialon
FleetTAB reads the Wialon account you already run. Nothing is migrated and Wialon stays the source of the data — FleetTAB adds screens on top of it. Without the connection there is no data source, so this is the first thing to set up.
There are two independent steps, and they are easy to confuse:
| Step | What it is |
|---|---|
| App login | Getting into FleetTAB itself, with your work email and a one-time verification code. Nothing to do with Wialon. |
| Wialon connection | Pointing FleetTAB at your fleet data. Done once, then reused automatically. |
The Wialon connection itself can be made two ways:
- Sign in with Wialon — authorize FleetTAB on Wialon's own sign-in page. Your Wialon password is never shared with FleetTAB, which makes this the simplest option for most accounts.
- Wialon API token — paste a 72-character token you generate yourself. Use this when you want to control exactly which units and data types FleetTAB can read.
Start with Connecting to Wialon, which walks through both and says which one fits your account.
Withdrawing access
Either route leaves you holding the key. Deleting the authorization in Wialon's own list of authorized applications cuts FleetTAB off immediately, without touching your Wialon password. The token page covers the access flags and the revocation steps.
For background on what a Wialon token is and which access level an integration actually needs, see How to Create a Wialon API Token.