FleetMonitoring Administrator Guide
This guide explains how to set up a fleet, connect Teltonika trackers and give users access to their vehicles. It applies whether you manage your own fleet or provide GPS tracking to multiple customers.
1. Sign In to the Administration Panel
Open the administration panel using the address and credentials provided for your deployment. Before you start, have the vehicle details, the model and IMEI of each tracker, and a list of the people who need access.
2. Set Up Your Fleet or Customer Account
If you monitor your own fleet, select your organisation’s account. Use vehicle groups to organise vehicles by branch, team or purpose.
If you provide GPS tracking to multiple customers, create a separate customer account for each company. Before adding a vehicle or user, check that you’re working in the correct account.
3. Add a Vehicle and Assign Its Tracker
- Open the vehicle or device management area for the relevant account.
- Create a vehicle record with a recognisable name, such as its registration number and fleet number.
- Enter or select the tracker identifier required by your deployment. Where the platform uses the IMEI, copy it from the device label or configuration.
- Assign the tracker to the correct vehicle and save the settings.
- Once the tracker is installed and powered, check that the vehicle appears on the map with a recent position.
The tracker must also be configured to send data to your FleetMonitoring server. If you’re moving a tracker from another platform, check its server settings and mobile connectivity before testing.
4. Add Users and Set Their Permissions
- Create an individual account for each person who needs access.
- Assign the appropriate role and select the vehicles or groups that person should see.
- Enable the functions they need for their work, such as maps, journey history or reports, where those permissions are available.
- Share the login address and provide their initial access details securely.
- Ask the user to sign in and confirm that the expected vehicles and functions are visible.
For customer accounts, check that each user can see only the vehicles they’re authorised to access. Use the User Guide to introduce the customer panel.
5. Check the Setup Before Handover
Open the vehicle in the user panel and check its name, latest position and last update time. If possible, take the vehicle on a short test journey and confirm that the journey appears in its history.
If the deployment includes reports, geofences or alerts, test those functions as well. For an alert, trigger the agreed test event and confirm that the intended recipient receives it.
6. Resolve Common Setup Issues
| What you see | What to check |
|---|---|
| The vehicle does not appear in the user panel | Check its customer account, group assignment and the user’s permissions. |
| The vehicle is visible but has no position | Check tracker power, mobile connectivity, server settings and the device identifier. |
| The last position is out of date | Compare the last update time with the tracker’s reporting schedule and check whether the device is currently sending data. |
| Fuel or other vehicle data is missing | Confirm that the vehicle, tracker and installation support the parameter and that the platform is configured to receive it. |
| A geofence is visible but no alert arrives | Check that an alert rule is enabled for the event and that the recipient and delivery settings are correct. |
7. Replace a Tracker or Remove Access
If you replace a tracker, confirm how the device reassignment will affect journey history before making the change. After assigning the replacement, check that it sends data under the intended vehicle record.
When someone leaves your team or no longer needs access, remove their permissions or disable their account, according to the options available in your deployment.
Contact Support
When reporting an issue, include the affected account or vehicle, the tracker model, the time of the last successful update and a short description of what happened. A screenshot can help identify where the issue occurs. Keep passwords out of the report.