> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/system-admins/administration/job-manager/settings.md).

# Settings

Review account, instance, product store, version, time zone, and data-fetch settings.

Open `Settings` to confirm the context used by Job Manager.

## Review your account

The profile card shows the signed-in user. Use:

* `Logout` to end the current session
* `Go to Launchpad` to return to the HotWax Commerce Launchpad
* `Go to Legacy App` to open the previous Job Manager experience

## Confirm the OMS instance

Review `OMS instance` before you run a job, upload a file, or change a configuration.

`Go to OMS` appears only when your sign-in provides access to the OMS interface and requires `COMMERCEUSER_VIEW`.

## Select a product store

Use `Select store` when the connected Order Management System has more than one product store.

Changing the product store refreshes supported job and file data. It does not apply a product-store filter to system messages.

## Review the app version

The `App` section shows:

* Version
* Build time
* `Update` when a newer installed app version is ready

Select `Update` to load the available version.

## Change the time zone

Job Manager uses the selected time zone for displayed timestamps and schedule interpretation.

1. Select `Change` in the `Timezone` card.
2. Search for a time zone.
3. Select the required time zone.
4. Save the selection.
5. Confirm the displayed current time.

Compare the browser time zone with the selected time zone before you edit a schedule.

## Refresh app data

Use `Data Fetch Status` to review each reference-data source and its record count.

* Select the refresh icon for one data source.
* Select `Refresh All` to reload every listed source.

Wait for the status to finish before you repeat a refresh.


---

# 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.hotwax.co/documents/system-admins/administration/job-manager/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.