> For the complete documentation index, see [llms.txt](https://help.aphex.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aphex.co/docs/frequently-asked/faqs.md). # FAQs


Planning	Where have my Tasks gone? How do I print my plan? Can I change the sort order of Tasks and Packages? Why can't I delete a Task? Why are the successors not scheduling? How do I promise Tasks? How do I delete multiple Tasks? Why were some Tasks skipped from updating?
Project Assets	How do I make changes in bulk? Why can't I upload an image for my Location? How do I change the non-working days of a Task? How do I Move Folders?
Users	How do I transfer my work to another User? How do I add new Users to the Project? What can Lite Users do? How do I set a reviewer? How do I reset my Password? How do I set up Multi-Factor Authentication?

--- # 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://help.aphex.co/docs/frequently-asked/faqs.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.