> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/manager-workstation/using-manager-workstation/logging-in-as-manager.md).

# Logging in as Manager

{% stepper %}
{% step %}
**Open Manager Workstation**

Open a web browser and connect to the Manager Workstation.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/FyXKcbL35FPkVQmvilm3/Unknown%20image)
{% endstep %}

{% step %}
**Employee Typ**

Select **\[Employee Type]** from the drop-down menu, then choose **Manager**.
{% endstep %}

{% step %}
**Manager credentials**

Enter the user name and password.

* User Name
* Password: (\*\* the current valid Manager password \*\*)
  {% endstep %}

{% step %}
**Sign in**

Press **\[Enter]**, or click **\[Sign In]**.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/UJ2Ed95XIFTDDNWr79YQ/Unknown%20image)
{% endstep %}
{% endstepper %}

When logged in as Manager, there is access to both the Cashier menu and the Manager Menu.

{% hint style="info" %}
The MWS functionality allows a Manager to enter a Cashier’s drawer count amounts. Under normal conditions, the cashier will routinely enter their own drawer counts. However, there may be situations where the drawer counts must be entered by the store manager either because the cashier is not available or because store policies and procedures require it. When the Manager takes this action, the same entry form will be used for tender counts as when logged in as a Cashier.
{% endhint %}

## Cashier Reporting

Navigate to Cashier > Cashier Reporting.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/uHUaGj8F5vLNiBQoLt5O/Unknown%20image)

The Manager’s Cashier Reports List shows all available Closed Cashier Reports within the reporting period for all cashier accounts.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/pAEy2MZsIjF4vYQpcUIp/Unknown%20image)

Reports are sorted with the most recent report at the top. Each record shows the associated cashier, register number, and the closed date and time.

Each entry shows the MOP Amounts Entry status: Pending or Complete.

The Manager may click any report number link for reports marked as Complete to print or reprint the Cashier Report.

The Manager may click to select any report number link to enter amounts for any reports marked as Pending. If more than one Report is “Pending”, the oldest report must be completed first.

## Editing Pending Reports

The Manager may click to select the link to any cashier’s reports marked as Pending to enter amounts.

The report header includes the Cashier ID and Name, the Report Sequence Number, the Register Number and the date/time stamp of when the report was closed.

The report body includes an entry for each MOP, configured to prompt for a cashier amount and provides a field into which amounts are entered.

The MOP configuration flag to permit zero entry is enforced in this form. MOPs configured to permit zero entry default to zero when no amount is entered.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/6dyXNnCyYM1jndfy9Ujm/Unknown%20image)

After counting the till, the Manager enters the counted amounts for Cash, Check, and Coupons.

Click **\[Save]** to save the form contents, or to exit without saving, click **\[Cancel]** to return to the Reports List screen.


---

# 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://commanderhelp.verifone.com/feature-references/features-and-products-references/manager-workstation/using-manager-workstation/logging-in-as-manager.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.
