> 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/user-guide/assignment.md).
# Assignment
An assignment is a part of a planning, and is used to tell who is doing what and when. It's about resource planning.
When you do your planning, you create assignments that will be linked to the plan. Creating assignments in Newsroom Planner means that you can add the assignment both to the planning and to the resources. It will be clear to you which plannings already have booked assignments and you do not risk that any planning is missing assignments.
If the assignment is to write an article, you can aslo create a draft of the article in the assignment. This means that the article already is created in the Writer when the reporter should start writing it. You can preview the article directly in the assignment.
Below is a calendar view of the assignments five days ahead. You get a good overview of how far one particular assignment has come in the flow because it is enriched with information depending on how much work has been done. As we described earlier in this guide, the look of the cards (colors, icons, text) is depending on what settings the admin user has made in your organization. In this guide you will see the default setting.
---
# 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/user-guide/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.
