> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/platform-administration/maintenance-mode-applications/snapper/lock-snapper-settings.md).

# Lock Snapper settings

Hide or disable Snapper settings for agents.

Use setting visibility and editability controls when agents must not see or change specific Snapper settings.

In the Snapper configuration, each setting can have two related controls:

| Control     | Effect                                                 |
| ----------- | ------------------------------------------------------ |
| **Enabled** | Controls whether the setting is editable or read-only. |
| **Visible** | Controls whether the setting is visible or hidden.     |

By default, all settings are visible and editable.

<figure><img src="https://2358142509-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJymOXTAFZLWXmwvtHWu8%2Fuploads%2Fgit-blob-8aee8e6ff2812c26fca13fa2dffcbfdfe67fff8e%2Fsnapper-show-hide-settings.png?alt=media" alt="Snapper setting visibility and enabled controls"><figcaption></figcaption></figure>

## Prerequisite

* Snapper v 8.2 or higher.

## Option 1: Edit config.xml

Edit the local Snapper configuration file:

```
%appdata%\Workstreampeople\Snapper\config.xml
```

Set the relevant `Enabled` or `Visible` field for the setting that must be controlled.

{% hint style="warning" %}
Changing the local `config.xml` affects the Windows user profile where the file is changed. Back up the file before editing it.
{% endhint %}

## Option 2: Use unattended installation parameters

During unattended installation, append `ENABLED` or `VISIBLE` to the setting name and set the value to `false`.

Example:

```powershell
msiexec /i c:\Install\Setup.msi /qn /norestart /log c:\Install\install.log ENABLEAUTOMATICANSWER="true" ENABLEAUTOMATICANSWERVISIBLE="false" ENABLEAUTOMATICANSWERENABLED="false" AUTOMATICANSWERINTERVAL="03" AUTOMATICANSWERINTERVALVISIBLE="false" AUTOMATICANSWERINTERVALENABLED="false"
```

The example:

| Parameter                                | Effect                                        |
| ---------------------------------------- | --------------------------------------------- |
| `ENABLEAUTOMATICANSWER="true"`           | Enables automatic answer.                     |
| `ENABLEAUTOMATICANSWERVISIBLE="false"`   | Hides the automatic-answer setting.           |
| `ENABLEAUTOMATICANSWERENABLED="false"`   | Makes the automatic-answer setting read-only. |
| `AUTOMATICANSWERINTERVALVISIBLE="false"` | Hides the interval setting.                   |
| `AUTOMATICANSWERINTERVALENABLED="false"` | Makes the interval setting read-only.         |

## Verify the lock

1. Start Snapper with a test user profile.
2. Open the relevant settings area.
3. Confirm that hidden settings are not visible.
4. Confirm that disabled settings are visible but cannot be changed.


---

# 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://atlas.anywhere.now/platform-administration/maintenance-mode-applications/snapper/lock-snapper-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.
