> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/documentation/modules/assistance/planning.md).

# Plannings

Planning view allows to display planned tasks attached to a ticket, a problem or a change as well as planned notes or plugins' planned elements.

This menu is only visible if profile includes `View planning` authorization.

Date and time slot can be selected. A filtering on objects to include in planning is also available.

Four views are available, depending upon user authorizations:

* Personal view : includes only the elements of the connected user;
* Group view: includes only the elements of the connected user's group, needs *See planning of group's persons* authorization;
* Users view: includes the planning of a particular user, needs *See all plannings* authorization;
* Groups: includes the planning of a particular group, needs *See all plannings* authorization;

This information can be exported in two formats:

* Ical, in order to integrate planning in third-party tool calendar;
* Webcal, which allows to subscribe a third-party calendar to GLPI planning.

{% hint style="info" %}

* Access to Ical and Webcal feed is protected by a security key integrated into the URL. It is possible to regenerate this key in menu `Preferences`. See [Manage preferences](https://help.glpi-project.org/documentation/readme-1-1/preferences.md).
* User's planning can be displayed on home page if profile has authorization *See my personal planning*. However, it is not possible to add an element to a planning from this interface; it is mandatory to plan a task or a note so that planning fills up.
  {% endhint %}


---

# 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.glpi-project.org/documentation/modules/assistance/planning.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.
