Frequently Asked Questions
Answers about deployment, data storage, trials, and online and offline licensing.
Your asset inventory and operational records are stored in the MongoDB database configured for your deployment. For an on-premises installation, use a database inside your own environment. For a cloud deployment, data resides in your configured hosted database. Connecting to Provider Admin sends organization, licensing, installation, and usage metadata; it does not move your full asset database to Provider Admin.
No paid license is required during the three-calendar-month trial. The trial provides Advanced plan access, including up to 1,000 assets, 500 users, and 3 administrators. One trial is available per installation. When the trial expires, activate an approved paid plan to continue using paid features; your existing data is preserved.
Generate an
activation_request.json file from the installed application and transfer it through your approved process to your provider. After reviewing and approving the request, the provider supplies a signed .lic file. Transfer that file back and import it into the same installation. Exporting a request or downloading a license does not activate the application; the signed file must be imported successfully.Obtain an activation code from your provider for your approved paid subscription. Open the application's subscription activation page, enter the code in the online activation form, and submit it while connected to the internet. The application requests a signed license, checks that it matches the installation, and stores the activation on the backend. This requires a connected MongoDB database and a deployment that supports online activation.
The application schedules an online license check after a successful activation or refresh, normally after one day. Each signed online license allows up to seven days between successful validations, capped by the subscription expiry. Reconnect before that allowance expires. For environments that cannot contact the provider, ask for the signed offline license workflow.
The application supports Windows EXE installations and cloud deployments. Each deployment uses its own installation and database identity. A website URL alone does not identify or activate a license. Tell your provider which deployment you intend to license and generate the activation request from that deployment.
Licenses are bound to installation details. Moving from a cloud deployment to an EXE, changing computers, or changing the database identity may require a new activation or replacement license. Contact your provider with an activation request from the new deployment before moving.
License status describes your subscription approval and validity. Installation status describes connectivity: Provider Admin shows an installation as inactive when it has not received a recent active heartbeat within 30 minutes. Check Settings > Provider connection, enrollment, internet access, and reporting status. Creating another license does not restore the reporting connection.
Contact your provider to approve the new plan, limits, and validity dates. For offline activation, obtain and import the updated signed
.lic file. For online activation, the application receives updated signed terms when it successfully refreshes, or your provider may supply a new activation code when a replacement is needed. Choosing a plan on the website alone does not activate it.Open your deployment's mobile audit scanner on your phone, allow camera access, and scan an asset's QR code. Verify its details and record the physical audit. The scanner automatically returns, ready for the next device. Your phone needs access to the deployment over HTTPS. Read the mobile audit steps.