> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/getting-started/the-logicnets-designer/change-the-order-of-projects.md).

# Change the Order of Projects

While the LogicNets system does not look for projects in a particular order some users like to organize the order in which their projects, logicnets, and resources appear in the Projects pane to make them easier to find or to follow whatever logic makes the most sense to the person controlling the pane.

1\. Click the folder or logicnet you would like to move.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-52a2a241330296d738bf81a21a51561cf0650404%2F26598114-6f33-41d9-b063-558103aa20c2.png?alt=media)

2\. Hover over the left side of your selection and you will see an icon of nine small dots in a square.

3\. Click on those dots and, still holding down your mouse button, pull the folder or logicnet into the location where you want it and release your mouse button.

Note: The system knows what types of items can live in a particular folder. It will not allow you to move a logicnet into a data table folder, for example.


---

# 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://community-test.logicnets.com/release-9/getting-started/the-logicnets-designer/change-the-order-of-projects.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.