> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-geolocation-credit.md).
# LCT - Geolocation Credit
The **Geolocation Credit** function allows tenant users to monitor and manage the geolocation credits used by **Low Cost Tracker (LCT)** devices.
Credits are managed at tenant level, allowing available capacity to be shared across the LCT device fleet while keeping consumption visible and controlled.
{% hint style="info" %}
This function applies only to **Low Cost Tracker (LCT)** devices. If your tenant does not contain LCT devices, the Geolocation Credit section is not applicable.
{% endhint %}
## Steps to Access Geolocation Credit
1. **Open the Cockpit Menu.**
2. **Select Administration.**
3. **Click Geolocation Credit.**
## How Geolocation Credits Work
Each LCT includes a defined geolocation-credit allocation according to the applicable contract.
Credit consumption follows this order:
1. **Device included credits**
2. **Purchased credit recharges**
3. **Tenant shared credits**
Because credits are managed at tenant level, available capacity can support devices with higher geolocation usage. Purchased credits are automatically available to devices requiring additional geolocation credits.
Credits included with the device are renewed yearly for the duration of the active contract.
GIoT also monitors tenant consumption and sends email notifications when usage reaches **80%** and **90%** of the available credits. Notifications are sent to the email addresses configured for the tenant in the **Administration** section.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-geolocation-credit.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
