What specific security clearance or user permission is required for a user to access the IOX Output Add-In and successfully enable/use the “Send” button?
The user already has access to the Add-In and can open it, but the “Send” button remains disabled. The user is assigned to only one group for testing purposes.
Has anyone configured this successfully without granting full Administrator access?
You need to be logged in to reply to this post and participate in the Geotab Community discussions.
@RReye-10434 I don't know for sure, but I have a vague memory that the IOX-Output uses Geotab's Message system under the hood, so try turning on Send Messages and see if that works?
Thanks for the suggestion.
I already enabled the "Send Messages" permission for the user, but the "Send" button is still disabled and the command cannot be executed.
The user can access the IOX Output Add-In and select the vehicle and state, but cannot send the command.
Is there any additional security clearance or permission required besides "Send Messages"?
Hey @RReye-10434 do you still need any help with this question?
No, thanks for your help. Now I need help with something else.
I have a lot of questions about asset linking when creating the association automatically. Let me explain: previously I worked for another company that was also implementing Geotab — actually, I implemented it from scratch, so I've learned a lot about the platform. In that previous job, the links were created automatically. Now that I'm at a new company, also using the platform, they're not being created automatically and have to be done through the Geotab Drive app. Do you know what I might be missing? All assets, both GO devices and Flex Solar units, are under the same work group. Could there be a setting I'm overlooking?
Great question! Sorry for the delay in getting back to you on this. This is almost certainly a database-level service setting rather than anything wrong with your configuration. Although without seeing your database I cannot be 100% confident this is it. It is just what I think makes the most sense. Support would be able to look at your database and the situation a lot better than we can in the community.
Geotab has two background services that handle automatic asset linking:
- The legacy AssetPairing service (older, being retired)
- The new AssetCoupling service (current, uses the modern AssetLink entity)
These two are mutually exclusive and controlled by a feature flag (EnableAssetCouplingGeneric) that has to be enabled per database. Your previous company likely had the new service enabled and that's why auto-linking worked there. Your new company's database may still be on the legacy service or may not have the auto-linking service enabled at all, which would explain why everything needs to be done manually through Drive.
First thing to check: Contact your reseller or Geotab support and ask them to confirm whether the asset linking / AssetCoupling service is enabled on your database. That's the most likely fix.
Beyond that flag, auto-linking has a few specific requirements that are worth validating:
1. Both devices must be moving together — assets that are stationary in a yard will never auto-link regardless of settings. The system needs to see them travelling together to establish the link.
2. ~15 minutes of movement data is required — the algorithm needs enough shared GPS fixes to be confident the devices are actually moving together, not just near each other. Short trips may not give it enough time.
3. Reporting mode on the Flex Solar units matters a lot — if those units are in a time-based reporting mode (e.g. every 8–24 hours), they won't be generating GPS fixes frequently enough while moving for the algorithm to detect co-movement. If possible, set them to movement-based mode so they report while in motion. Wired/powered units will link much faster than battery-only units since they report as frequently as a GO device.
4. Same work group helps but is probably not the root cause here — that was more of a factor in the legacy service.
The short version: start with your reseller to check the database service flag. If that's enabled and it's still not working, the Flex Solar reporting mode is the next thing to look at.
Feel free to reach out if you have any other questions or run into any issues getting into contact with support or your reseller.
wow this information is a amazing, Is the EnableAssetCouplingGeneric feature flag something that any reseller can request to have enabled, or is it currently being rolled out only to specific databases?
Hi,
Thank you for your help.
You were absolutely right. After contacting our Geotab support team, they confirmed that the issue was related to a database-level setting. They enabled the required Asset Coupling configuration in our database, and the automatic asset linking is now working correctly. We now have this feature enabled and working as expected.
I really appreciate your guidance—it pointed us in the right direction.
I have one more question: now that Asset Coupling is enabled, is there any way to configure a rule, exception, or notification that alerts us if the link between the tractor and trailer is broken or if an asset becomes unlinked? We'd like to be notified immediately whenever the automatic asset association is lost.
Thanks again for your support!