> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/devices-and-settings/object-management/change-plan.md).

# Change plan

Switch the service plan for a GPS device in Navixy. Review available plan options and select the one that matches your operational and data needs.

Assigns a device's pricing plan (tariff), which determines its billing and which features and settings blocks are available.

## Changing the plan

To change your plan, follow these steps:

1. Navigate to the **Change plan** block within the **Devices and settings** panel.
2. Click on the **Change plan** button.
3. Review the available plan options. Choose the plan that aligns with your operational requirements.
4. Once you've selected the desired plan, click **Save** to apply the change.

## Availability

Appears on accounts where plans/balances are visible. The plan selector is hidden on accounts where balances and plans are hidden, and for clone devices.

{% hint style="info" %}
A device's plan determines which other settings blocks are available, some blocks require a plan feature (for example, [data forwarding](/docs/user/guide/devices-and-settings/connectivity/data-forwarding.md) or [working statuses](/docs/user/guide/devices-and-settings/object-management/working-statuses.md)).
{% endhint %}


---

# 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://navixy.com/docs/user/guide/devices-and-settings/object-management/change-plan.md?ask=<question>&goal=<user_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.