> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/getting-started/quick-start/updates.md).

# Updates

Keeping software updated will ensure you have all the newest features available.

## How to

{% hint style="info" %}
Before updating we recommend to finish your ongoing projects.\
\
In rare cases working on a project with multiple tool versions might cause conflicts that will have to be addressed individually.\
\
If you have noticed any issues on an ongoing project after an update - please try to revert to the previous version manually as described [here](https://docs.besmart.software/getting-started/faq/how-to-revert-to-a-previous-version-of-a-tool) and/or reach out to our technical support team at <https://emea.support.arkance.world/hc/en-gb/requests/new>
{% endhint %}

1. Open your ARKANCE Dock.
2. Navigate to the "Updates" tab ("refresh" icon in the bottom menu).
3. Available updates will be visible.
4. Choose to either "Update all" or an individual tool.

<figure><img src="https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2F7hNAH2G9B77Vd8igNuUc%2F2025-03-10%2009_44_26.png?alt=media&amp;token=fbf1e25e-5a08-44f0-84ca-8b18634ede37" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
Updates" tab will display available updates for your ARKANCE Dock and any individual tools.
{% endhint %}

{% hint style="success" %}
If no updates are visible - you are already up to date!
{% endhint %}

<details>

<summary>How to revert to an older tool version?</summary>

A version that you already had installed will remain on your device.\
You can manually revert to the version by removing/moving the newest version installation folder. More details [here](https://docs.besmart.software/getting-started/faq/how-to-revert-to-a-previous-version-of-a-tool).

</details>

<details>

<summary>Having troubles?</summary>

1. Installation files are stored online. Please make sure that your device/network/security measures allow connection to:\
   a. <https://d3pwddx1voa37u.cloudfront.net/\\*\\>
   b. <http://cdn.iv.agacad.com/\\*\\>
   \
   More needed URLs and details can be found [here](https://docs.besmart.software/getting-started/troubleshooting/unexpected-error-occurred).
2. Reach out to <https://emea.support.arkance.world/hc/en-gb/requests/new> for personal assistance

</details>


---

# 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.besmart.software/getting-started/quick-start/updates.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.