> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/releases/old/3-50-2.md).

# 3.50.2

Release Date: June 26, 2023

## **Central Manager and Store Manager**

### Enhanced security for Manager User Roles

Starting with release 3.50.2, you can configure **Full Access**, **No Access**, or **View Only** access for specific privileges under **Manager User Roles**. In previous releases, you could only configure Full Access or No Access for specific privileges. If you configure View Only access for a privilege, the person assigned to that role can only view records. They cannot edit, delete, copy, or create new records.

<div align="left"><figure><img src="/files/JPhmyWMQN6D0HcPKX18J" alt=""><figcaption></figcaption></figure></div>

If you set up Manager User Roles in an earlier version of RMH and you upgrade to 3.50.2 or later, the preexisting roles and privileges are preserved. If you want to utilize the new View Only option for privileges, you will need to edit the preexisting roles or create new roles.

### New option for linking to item pictures

Starting with release 3.50.2, if you want to link an item to a picture, you now have the option of entering either the **file path (including the file name)** or the **file name** in the **Picture** field. You can access the Picture field under **Merchandising** | **Items** on the **Special** tab.

<div align="left"><figure><img src="/files/FMd5zwCArxGn6JYzbByb" alt=""><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="/files/jPBAPsHirLu5OHRulkQM" alt=""><figcaption></figcaption></figure></div>

If you prefer to enter only the file name, the file must be saved to the **Pictures** folder. You must also make sure the path to the Pictures folder is configured in the Administrator app. To configure the Pictures folder, open **Central Administrator** or **Store Administrator** and click **Configuration**. On the **Path** tab, in the **Pictures** field, enter the path to the Pictures folder, then click **Save And Close**.

{% hint style="info" %}
The Pictures folder is usually located at C:\Program Files (x86)\Retail Hero\RMH Central Manager\Pictures or C:\Program Files (x86)\Retail Hero\RMH Store Manager\Pictures.
{% endhint %}

<div align="left"><figure><img src="/files/aSNZMQmq5EGf2PMOjSCV" alt=""><figcaption></figcaption></figure></div>

### New option to enable/disable customer lookup in RMH Central

Starting with release 3.50.2, you can select a new option **Do not allow customer lookup in RMH Central** to prevent POS from looking up customers in RMH Central.

<div align="left"><figure><img src="/files/IxEck953ltloJp3iKnUN" alt=""><figcaption></figcaption></figure></div>

When this option is selected, the **Lookup Online** button in POS is disabled and the cashier can only look up customers in the local store database.

<div align="left"><figure><img src="/files/mmobNKtcUSvoUg2W0rdW" alt=""><figcaption></figcaption></figure></div>

This new option is available in Store Manager under **File** | **Configuration** | **Store Rules** | **Customer Options**.By default, this option is not selected if you upgrade to 3.50.2 or later.

If the **Do not allow customer lookup in RMH Central** option is not selected, the **Lookup Online** button in POS is enabled and, when it is clicked, POS will look up the customer in the Central database.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rmhpos.com/releases/old/3-50-2.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
