> For the complete documentation index, see [llms.txt](https://docs.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dispel.com/changelog/earlier-releases/2024-03-15.md).
# 15 March 2024
Device Accounts
## 15 March 2024
{% hint style="info" %}
Published on dispel.com.
{% endhint %}
## Device Accounts
### Device Accounts
Device Accounts streamline the process of logging into remote devices while eliminating the need for users to handle sensitive credentials directly. Dispel administrators can create Device Accounts by supplying the necessary authentication credentials and configuring the protocols and ports the account can utilize on the associated device. Furthermore, administrators can specify which Dispel members are permitted to connect using the Device Account. Credentials are encrypted in specialized storage and are never stored in the Dispel database.
By using Device Accounts, the risk of breaches is significantly minimized as it reduces the number of individuals with access to sensitive account credentials. Device Accounts also expedite access to remote devices by enabling users to log in with just a single click.
### Fixes & improvements
* Updated our Mandarin, French, German, Portuguese and Spanish Language Translations
* Addressed several navigation and scrolling issues throughout the Dashboard
* Fixed a bug that resulted in the wrong email address being displayed when an Access Window is created
* Improved usability by moving Group Devices to the top of the device list when ACLs are activated on them
* Improved the page load experience for ACLs when there are many ACLs configured
* We now log an event when Users, Regions, Facilities, Groups, and Devices are deleted
* Clarified the error messages associated with inviting new users to give better guidance on remediation
* We now prevent existing Users from re-using VSO links
* Fixed a bug that was preventing the filtering of Stacks
---
# 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.dispel.com/changelog/earlier-releases/2024-03-15.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.
