> 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/glpi-12/tools/rssfeed.md).

# RSS feeds

GLPI allows you to include RSS feeds on the tool's homepage.

<figure><img src="https://304570660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fuys4bnfAs7Oe2yWUUh3p%2Fuploads%2Fgit-blob-f295a51d06200cf835a81e7a59219715530c555e%2Frss-personnal-view.png?alt=media" alt=""><figcaption><p>Personnal view RSS</p></figcaption></figure>

An RSS feed is, by default, personal and therefore only visible to its creator.

For an RSS feed to become public and visible to other users, targets must be added to it. A target is an entity, a group, a profile, or a user.

{% hint style="info" %}
A public RSS feed is visible to users associated with a profile if that profile has read permission for public RSS feeds.
{% endhint %}

***

## Adding Feeds

* To add an RSS feed, click **`+ Add`**
* Add the URL
* Mark your feed as active
* You can select a value in the **Number of items displayed** field

<figure><img src="https://304570660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fuys4bnfAs7Oe2yWUUh3p%2Fuploads%2Fgit-blob-19e2891013b2de4bdd87304cd1656858235b02e1%2Frss-add-feed.png?alt=media" alt=""><figcaption><p>Add new RSS Feed</p></figcaption></figure>

***

## Deleting Feeds

You can click **`Delete permanently`** from the feed in question or use the **mass action** to delete one or more feeds at the same time.

<figure><img src="https://304570660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fuys4bnfAs7Oe2yWUUh3p%2Fuploads%2Fgit-blob-1ee898c09435e3d2a8ec5e60ea88dbd79a4b2f77%2Frss-delete-feed.png?alt=media" alt=""><figcaption></figcaption></figure>

***

## Content

This tab allows you to view the number of items displayed; this content is what is shown on the homepage.

<figure><img src="https://304570660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fuys4bnfAs7Oe2yWUUh3p%2Fuploads%2Fgit-blob-ad327bf1dd12acc4256789b45abc7052f3d5c84c%2Frss-content.png?alt=media" alt=""><figcaption><p>RSS content</p></figcaption></figure>

***

## Targets

This tab allows you to view and modify the list of targets for the RSS feed.

You can add entities, groups, profiles, and users.

<figure><img src="https://304570660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fuys4bnfAs7Oe2yWUUh3p%2Fuploads%2Fgit-blob-d98fe6e8b1fb67052c7440599bfabc2aac3527de%2Frss-target.png?alt=media" alt=""><figcaption><p>Add taget</p></figcaption></figure>

***

## History

The *History* tab is used to display all modifications made to an item. The following information about modifications is available:

* Modification ID.
* Date and time of the modification.
* User who made the modification. If this field is not populated, it means the action was performed automatically (e.g., automatic inventory update).
* Field that was modified.
* Description of the modification that was made.

The modification description represents either the difference between the old and new value (e.g., for the location field: Change from HQ to Remote Office A), or the explanation of the action that was performed (e.g., Software uninstallation: "Gimp 2.0").

{% hint style="info" %}
For dropdown lists or objects with a parent/child relationship, a child modification will appear in the parent item's history.
{% endhint %}

***

## All

For an item, all information is displayed on a single page from the *All* tab. This shows all the tabs of an object's form in a single view, one below the other.


---

# 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/glpi-12/tools/rssfeed.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.
