> 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/central-manager/configure-stores/about-store-authentication.md).

# About store authentication

When you add stores to Central Manager, you have the option to enter a **Store Key**, which is used in combination with the **Store ID** to authenticate the store to Central Manager. If you do not enter a Store Key, only the Store ID is used for store authentication.

If you choose to use the Store Key and Store ID for authentication, if authentication fails for one or both values, the store's connection to Central Manager will fail and data synchronization will not take place.

Using Store Key for store authentication is optional. If you upgrade a customer to release 3.51.4 or newer, they are not required to enter a Store Key for stores. However, using a Store Key for store authentication is recommended for all centrally-managed stores to improve security.

If you choose to use Store Key for store authentication, you must first add the Store Key in Central Manager and then restart the Central Server services. After you have confirmed that the Central Server services are running, you can then add the Store Key in Central Client.


---

# 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/central-manager/configure-stores/about-store-authentication.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.