> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/the-admin-panel/settings/general-settings-app-+-vp-1/integration-settings.md).

# Integration settings

{% hint style="info" %}

#### This page contains settings for existing integrations.

To connect a new service or manage integrations, use the Integrations page.

**→ Go to** [Integrations](/adding-users-and-ticketing/integrations.md)
{% endhint %}

### Location 

&#x20;<kbd>Settings</kbd> →  <kbd>General Settings</kbd> →  <kbd>Integration settings</kbd>

***

<details>

<summary>Show RSS feed items on social wall</summary>

**Purpose:** Display external content such as news, blog posts, or announcements alongside user-generated posts on the Social Wall to keep the feed informative and up to date.

**Input:** Boolean (True/False)

**Default value:** False

**Behaviour:**&#x20;

When enabled, posts fetched from configured RSS feeds are displayed directly in the main Social Wall feed alongside user-generated submissions.

When disabled, RSS feed items are available only via their dedicated navigation item and are not included in the main Social Wall feed.

{% hint style="info" %}
**Info**: RSS feeds must be configured before content can appear on the Social Wall.

**Go deeper:** Visit [RSS Feeds ](/adding-users-and-ticketing/integrations/rss-feeds.md)to learn about how to set up RSS feeds and how content is displayed on the Social Wall.&#x20;
{% endhint %}

</details>


---

# 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://knowledge-base.letsgetdigital.com/the-admin-panel/settings/general-settings-app-+-vp-1/integration-settings.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.