> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/sa6-notes/archive/features-archived-notes/advanced-tools.md).

# Advanced Tools

#### Purpose

Gives support staff and field technicians (not end users) direct access to SA6's internal state for troubleshooting: the effective merged configuration, the local event/database history, and the ability to manually fire test events.

#### Location 

\*\*Screenshots\*\*

ui/advancedTools

* configFile screen
* databaseViewer screen
* event generation screen
* override settings

#### Responsibilities

* Config Viewer — displays the effective, merged SupportAgentConfig (result of the full configuration cascade), so a technician can confirm what config the device is actually running without pulling files off the device.
* Database Viewer — browses local Room tables directly (event history, backup queue, sensor/status tables) — the same data model documented in Architecture → Local persistence.
* Event Generation — manually triggers any event type for testing the pipeline end-to-end (e.g. confirming Splunk/EMS delivery is working) without waiting for the real trigger condition.
* Override Settings — local-only overrides for a subset of settings (OverrideSettingsHelper), for testing without changing the real managed configuration.

#### Access control

Reached from the app via an admin-password gate. Long press toolbar nav.


---

# 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.bluefletch.com/bluefletch-enterprise/product-guides/sa6-notes/archive/features-archived-notes/advanced-tools.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.