> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/admin-console/settings.md).

# Settings

Inforiver offers multiple configuration options related to writeback/sync, managed DB etc. Let's go through each of these in detail.

**1. General** - You can configure the subscription-related settings including insights and comments. To learn more, refer to [general](/admin-console/settings/general.md).

**2. Forecasts**- You can configure auto-close settings for forecasts. [Learn more about forecast settings](/admin-console/settings/forecast.md).

**3. Holidays** - Admins can create custom holiday calendars that can be used to auto-close forecasts or keep subscription jobs on hold. [Learn more about holiday settings](/admin-console/settings/holidays.md).

**4. API token** - Admins can create API tokens to trigger subscriptions or refresh semantic models via API calls. [Learn more about API tokens](/admin-console/settings/api-token.md).

**5. Writeback/sync** - You can configure and manage all your subscription connections and their settings. To learn more, refer to [writeback/sync](/admin-console/settings/writeback.md).

**6. Inforiver managed DB** - Here you can learn about Inforiver managed Azure SQL database connection for writeback POC purposes. To learn more, refer to [managed DB](/admin-console/settings/managed-db.md).

**7. Assets** - Manage all the assets in the Inforiver visual in a single dashboard. To learn more, refer to [assets](/admin-console/settings/assets.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.inforiver.com/admin-console/settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.