> For the complete documentation index, see [llms.txt](https://docs.terrakube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terrakube.io/user-guide/projects/workspace-assignment.md).
# Workspace Assignment
Workspaces can be optionally assigned to a project. Assigning a workspace to a project lets you apply project-level team permissions and keeps related workspaces organized together.
### Assigning a Project when Creating a Workspace
When going through the workspace creation wizard, select a project from the **Project** dropdown. This field is optional — selecting **(No project)** leaves the workspace unassigned.
### Changing a Workspace's Project
To move a workspace to a different project or remove its project assignment, open the workspace and go to its **Settings** page. Find the **Project** field and select a new project or clear the selection, then save.
{% hint style="info" %}
Moving a workspace between projects requires the **Manage Workspaces** permission at the organization level, regardless of your project-level role.
{% endhint %}
### Filtering Workspaces by Project
On the workspaces list page, use the **Project** dropdown filter to show only workspaces belonging to a specific project. Select **Unassigned** to show workspaces that have not been assigned to any project.
### Project Badge on Workspace Cards
Each workspace card in the list displays the name of its assigned project as a badge. Workspaces without a project assignment show no badge.
---
# 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.terrakube.io/user-guide/projects/workspace-assignment.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.
