> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/newsroom-planner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/newsroom-planner/6.0.2/text-assignments.md).
# Text assignment
When you work with text assignments they could have three different looks depending on what information they have.
1. No article is yet created on your text assignment
2. An article is created. In the same plan, there is also a photo assignment but with someone else as the assignee.
3. An article has been created on your assignment.
Let's take a closer look on example one and two above.
### Example no 1
On an assignment you will see information on both the assignment and the plan. In this first example there is no article yes created. You see:
1. The title of the plan.
2. The status of the plan.
3. A chevron where you can collapse the plan.
4. A menu where you can create additional assignments within the plan and copy the plan.
5. You see the title and the time for the assignment.
6. A menu where you can create an article or set the assignment as Done.
### Example no 2
The difference in no 2 compared to no 1 is that there is already an article created on the assignment (1). There is also a photo assignment (2) that belongs to the same plan as your text assignment belongs to. In the case below, the assignee for the photo assignment is not you, but you can use the photos in your article, when the assignee has uploaded them to the assignment.
---
# 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.navigaglobal.com/newsroom-planner/6.0.2/text-assignments.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.
