> For the complete documentation index, see [llms.txt](https://docs.nuvens.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nuvens.cloud/architecture/workspaces-manager-architecture-guide.md).

# WorkSpaces Manager Architecture Guide

This document describes the architecture of Nuvens WorkSpaces Manager solution for Amazon WorkSpaces Personal, Pooled and Secure.

WorkSpaces Manager is a comprehensive internal tool to help customers to manage and migrate AWS WorkSpaces at scale. WSM will ensure the Amazon WorkSpaces environment is more secure, providing a deeper understanding of user behaviour whilst always ensuring the WorkSpaces estate is cost optimised.

This document has been produced for general use to understand the design and governance when deploying and managing WorkSpaces Manager in an Enterprise environment at scale.

The four main pillars of functionality for WSM are:

* [Management](https://docs.nuvens.cloud/architecture/workspaces-manager-architecture-guide/management.md)
* [Administration Tools](https://docs.nuvens.cloud/architecture/workspaces-manager-architecture-guide/administration-tools.md)
* [Cost Optimization](https://docs.nuvens.cloud/architecture/workspaces-manager-architecture-guide/cost-optimization.md)
* [Automation](https://docs.nuvens.cloud/architecture/workspaces-manager-architecture-guide/automation.md)


---

# 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.nuvens.cloud/architecture/workspaces-manager-architecture-guide.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.
