Configure localization preferences, application-wide behaviour, payment gateway credentials, data retention, and user-facing legal policies in Open VTS.
Last updated August 19, 2026
The System Settings section controls how Open VTS appears and behaves across the platform.
Following setting are covered saparately
Following Settings are covered in this page
These settings apply at the platform level and should be managed only by an authorized Superadmin.
Go to:
Settings → Localization Settings
Localization Settings control the language, date and time presentation, measurement units, theme, timezone, and default map location used across Open VTS.

The Live Preview shows how the current settings will appear before they are saved.

It displays:
Use the preview to confirm that the configuration is correct.
Select the primary language used by the platform.

Changing this setting updates the default interface language where translations are available.
Choose how text is displayed:


Use RTL for languages that are written from right to left.
Select the preferred date display format.

For example:
The selected format is used where dates are displayed throughout the platform.
Use the 24-hour clock toggle to choose between:

Select the timezone used for:

Live tracking, logs, replay, and other real-time interface elements may continue to use the browser or device’s local time.
Choose the measurement unit used across the platform:

This setting affects distance and speed values displayed in maps, reports, histories, and other relevant sections.
Select the default appearance:

The System option follows the appearance setting of the user’s device or browser.
Set the default location displayed when the map opens.

Enter:
The zoom level controls how closely the map is focused on the selected location.
A lower zoom value shows a larger area, while a higher value shows a more detailed local view.
Open VTS provides predefined locations such as:

Select a preset to automatically fill the map focus coordinates.
You can then adjust the latitude, longitude, or zoom manually.

Select Save to apply the changes.
Select Reset to return the fields to their previously saved values.
Go to:
Settings → Settings
The Application Settings page controls platform-wide behaviour, signup access, reverse geocoding precision, database backup retention, and operational-data cleanup.

The Current Configuration panel provides a summary of important settings, including:
This summary helps the Superadmin review the active configuration quickly.
Use the Demo Login toggle to enable or disable demo access.

When enabled, users may access the available demo environment without using a standard production account.
Disable this option when demo access is not required.
Reverse geocoding converts vehicle coordinates into readable addresses.

Select the required precision:
Higher precision may produce more detailed location results but can also increase geocoding usage.
Select how long system backups should be retained.

Available periods may include:
Choose a duration based on your operational, storage, and compliance requirements.
Older backups may be removed after the selected retention period.
The Signup Configuration section controls whether new users can register on the platform.

Enable this option when public or permitted self-registration should be available.
Disable it when accounts should be created only by authorized platform administrators.
Enter the number of credits automatically assigned to a new account after registration.
Example: Set this value to 50 when each newly registered account should begin with 50 credits.
Review this value carefully before enabling public signup.
The Data Retention section allows the Superadmin to identify and remove old operational telemetry and log records.

Data older than the configured retention period may become eligible for permanent deletion.
Core records such as users, vehicles, devices, drivers, documents, settings, licences, integrations, and credit history are not included in the operational-log cleanup described on this page.
Select Preview cleanup to calculate how many records are eligible for deletion.

This does not delete any data.
Always run a preview before starting a cleanup.
Select Run dry-run to simulate the cleanup process.

A dry run helps confirm what would be removed without performing the actual deletion.
Select this option only when the preview and dry run have been reviewed.

This action permanently deletes eligible operational telemetry and log data.
Important: Permanent deletion cannot be undone. Confirm that required backups are available before proceeding.
Select Save to apply the configuration.
Select Reset to discard unsaved changes and restore the previously saved values.
Go to:
Settings → Payment Gateway
The Payment Gateway page is used to enable a supported payment provider and store its required credentials.
The complete payment-provider onboarding and webhook setup depends on the selected gateway. This section explains only what must be entered in Open VTS.
Open the Gateway dropdown and select the required payment provider.

The available fields will appear according to the selected provider.
Turn on the gateway toggle when the configuration is ready to be used.
Keep it disabled while credentials are incomplete or still being tested.
For a provider such as Stripe, Open VTS may request:
The public key used by the application interface to initialize payment-related functions.
The private server-side key used to authorize secure payment operations.
Never display or share this key publicly.
The signing secret used to verify that webhook events were sent by the payment provider.
Obtain all credentials directly from the selected payment provider’s dashboard.
After entering the required credentials:
Important: Do not expose secret keys or webhook secrets in screenshots, documentation, emails, or support tickets.
The full payment setup may also require configuration inside the provider’s own dashboard, including account verification, currencies, payment methods, callback URLs, and webhooks.
Go to:
Settings → Update User Policy
The User Policy Management page allows the Superadmin to create and maintain the legal agreements displayed to platform users.

Select the policy that needs to be reviewed or updated:
Each policy is managed separately.
To update a policy:
The updated content becomes available to users after it is saved.
Use clear headings and readable paragraphs when writing policy content.
Select Reset All to discard unsaved changes and restore the previously saved policy content.
Each policy should match the actual operation of your business.
Avoid using generic or incomplete placeholder text.
The policies should clearly explain matters such as:
Legal policies can create contractual and regulatory obligations. Have the final text reviewed by a qualified legal professional before publishing it.
For a new Open VTS installation, configure these sections in the following order:
Confirm that: