> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/resources/other-resources/devolutions-terminology-changes.md). # Devolutions terminology changes Devolutions terminology changes explain renamed solutions, including Devolutions Cloud, workspaces, and Devolutions Password Manager. Some Devolutions solutions and features have been renamed. This article explains what changed and what the new names refer to. #### Devolutions Hub Business is now Devolutions Cloud Devolutions Hub Business has been renamed to Devolutions Cloud. The solution is the same, only the name has been changed to better reflect the nature of the workspace. #### Data sources are now called Workspaces The term "data source" has been replaced by "workspace" throughout Devolutions solutions and documentation. A workspace refers to the same concept as before: a connection to a data repository such as a database or a cloud-based vault. #### Devolutions Workspace is now Devolutions Password Manager The Devolutions Workspace application has been renamed to Devolutions Password Manager. This includes the desktop app, the mobile app, and the browser extension. --- # 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.devolutions.net/resources/other-resources/devolutions-terminology-changes.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.