# Settings

Control the existing installation, its sources, stored data, updates, and background work.

Use these guides to control the installation on your computer. Some settings are terminal commands or launch environment variables. They are not all switches in the Galaxy interface.

## Find the right control

### [Vault and storage](/docs/vision/settings/vault)

Check the selected Vault or understand retained records.

### [Permissions and source controls](/docs/vision/settings/permissions)

Enable an app, stop automatic connection or collection, or revoke provider access.

### [Updates](/docs/vision/settings/updates)

Update the installed product or check handbook freshness.

### [Privacy and feedback](/docs/vision/settings/privacy)

Understand data boundaries and control optional telemetry.

### [Troubleshooting](/docs/vision/settings/troubleshooting)

Diagnose a failed command, source, or query.

### [Background host and reliability](/docs/vision/settings/reliability)

Start, stop, or recover the background host.

### [Remote access](/docs/vision/reference/remote-access)

Connect from another computer.

## Inspect before changing

Start with the installed version and the existing Vault:

```sh
indra --version
indra --root "/absolute/path/to/your/Vault" status
```

Use the same absolute path for later commands. If your `zortex` command has the correct saved binding, it can resolve that root automatically. A new directory creates a different product context; it is not a repair for a missing connection.

Open **Local connection help** for source setup:

```sh
indra --root "/absolute/path/to/your/Vault" help
```

Open **Galaxy** for its app list, source details, and collection progress:

```sh
indra web --root "/absolute/path/to/your/Vault"
```


### Use the supported controls

The current Galaxy adapter does not provide working source switches, marketplace installation, in-app chat, or cloud-link provisioning in those panels. Use the documented help or terminal route for those tasks.

## Understand four different changes

| Change | What it does |
| --- | --- |
| Stop a running host | Stops that owner and its current services; it can be started again. |
| Disable login startup | Prevents automatic startup at login; it does not stop a host already running. |
| Disable a source | Stops its provider while retaining collected data. |
| Revoke account or remote access | Removes that access route; existing retained or shared copies may remain. |

Do not substitute one for another. When changing a launch setting, restart the relevant host or client so it receives the new environment. When changing a source, verify its current state and one relevant operation afterward.

The handbook defines the intended experience. An unavailable control or failed operation remains a product gap; it is not a reason to redefine success. Current availability is described beside the relevant procedure.
