> 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/introduction/job-manager-app.md).

# Job Manager app

Review verified access and action permissions for the current Job Manager app.

Job Manager uses app access, administrator permissions, and backend action checks.

## Grant app access

Assign `JOB_MANAGER_ACCXUI_APP_VIEW` to users who need to open Job Manager.

The app checks this permission during sign-in. A user without app access cannot use the operational pages described below.

## Review verified permissions

| Permission                    | Current use                                                                                                   |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------- |
| `JOB_MANAGER_ACCXUI_APP_VIEW` | Open the Job Manager app                                                                                      |
| `COMMON_ADMIN`                | Create, edit, save, and delete `Message types` and `Remote systems`, including protected configuration fields |
| `COMMERCEUSER_VIEW`           | Use `Go to OMS` from `Settings` when that button is available in the connected environment                    |

## Review job-specific access

A service job can show `Permission Group` on its Job Details `Overview` tab. The backend can require this job-specific permission before a user runs or manages that job.

Grant only the permission group required for the user’s operational role.

## Understand page access

After app access is granted, the current menu contains:

* `Dashboard`
* `Catalog`
* `Run history`
* `File history`
* `Manual uploads`
* `Message history`
* `Message types`
* `Remote systems`
* `Documents`
* `Export history`
* `Settings`

Some actions also depend on record state and backend authorization. The app shows only actions available for the current user and record.

## Protect integration settings

Remote-system definitions can contain secrets. Give `COMMON_ADMIN` only to users who maintain integration configuration.

Do not include secrets, payloads, or customer data in permission screenshots or access requests.

## Learn the current workflows

See the [Job Manager guide](https://docs.hotwax.co/documents/system-admins/administration/job-manager.md) for task-based instructions.


---

# 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/introduction/job-manager-app.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.
