> For the complete documentation index, see [llms.txt](https://docs.mathewscompany.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mathewscompany.com/pinnacle-2020/pinnacle-20-or-20-controls/system-settings/overview.md).

# Overview

At the bottom of the Pinnacle 20|20 Home page, there are 3 tabs: System Settings, Historical Data, and Troubleshooting. Pressing any of these 3 tabs will cause the tab to turn red and a different set of options, shown as red tiles, to appear. These options will change if a different tab is selected. The Pinnacle 20|20 control system has features that are customizable with several settings that can be changed as necessary. The System Settings tab are where these customizable features can be found. These features will be explained in detail as well as how to properly set them.

<figure><img src="https://2786764682-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQuAD4cJGmByvZ0oa7oPk%2Fuploads%2FscYymvmGbORIM5TrqYxp%2FHome%20Screen_System%20Settings%20Menu.png?alt=media&amp;token=54a7b967-ad82-4cad-bdfb-1fa42f28ad7e" alt="" width="563"><figcaption></figcaption></figure>


---

# 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.mathewscompany.com/pinnacle-2020/pinnacle-20-or-20-controls/system-settings/overview.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.
