> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/technical-guide/getting-started-guide/member-registartion-configuration.md).

# Member Registration Configuration

One of the main setup steps is choosing the registration method. See the sample example how this can be configured. Links to more detailed instructions can be found at the end of the article.

## How this example works

OpenLoyalty supports multitenancy, allowing each tenant (store) to operate as a distinct database, complete with its own member list and campaigns. This guide outlines the initial step of the setup process: selecting the appropriate registration method for a member. A single unique identifier is required, which can be an email, phone number, or loyalty card number (that can serve as your own unique identifier).

***

## Try yourself <a href="#to-try-it-yourself" id="to-try-it-yourself"></a>

* Input the previous saved [token](/technical-guide/getting-started-guide/authentication.md) in the request header
* Retrieve a list of [tenants (stores)](/administration/settings/tenants.md)\
  Endpoint: `GET /api/store`
* Choose the required tenant and its code
* Retrieve member registration for the specified tenant\
  Endpoint: `GET /api/{storeCode}/settings`
* Update `identificationMethod`\
  Endpoint: `PATCH /api/{storeCode}/settings`

  ```

  {
      "settings": {
          "identificationMethod": "phone" // or "loyaltyCardNumber", "email"
      }
  }

  ```

Moving forward, the chosen method will be a required field for member registration.

{% hint style="info" %}
Please ensure the proper configuration of the tenant. You can find out more [in this article](https://help.openloyalty.io/main-features/members/member-list/configuration).
{% endhint %}

***

## Endpoints used

{% openapi src="/files/jvocRY6tlAWocBwKFsNL" path="/api/store" method="get" %}
[openapi-5.61.0 (1).json](https://123136216-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgIv2CyIIYf7vRfuhMKQ6%2Fuploads%2Fgit-blob-c6d6d1ae03b533a9dcf7bf7e18c3fbc4e23b0e6b%2Fopenapi-5.61.0%20\(1\).json?alt=media)
{% endopenapi %}

{% openapi src="/files/jvocRY6tlAWocBwKFsNL" path="/api/{storeCode}/settings" method="get" %}
[openapi-5.61.0 (1).json](https://123136216-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgIv2CyIIYf7vRfuhMKQ6%2Fuploads%2Fgit-blob-c6d6d1ae03b533a9dcf7bf7e18c3fbc4e23b0e6b%2Fopenapi-5.61.0%20\(1\).json?alt=media)
{% endopenapi %}

{% openapi src="/files/jvocRY6tlAWocBwKFsNL" path="/api/{storeCode}/settings" method="patch" %}
[openapi-5.61.0 (1).json](https://123136216-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgIv2CyIIYf7vRfuhMKQ6%2Fuploads%2Fgit-blob-c6d6d1ae03b533a9dcf7bf7e18c3fbc4e23b0e6b%2Fopenapi-5.61.0%20\(1\).json?alt=media)
{% endopenapi %}

***

## More resources

For a detailed overview and description of the member registration configuration, please refer to these articles:

{% content-ref url="/spaces/cNVX03KZzmrGwJihLiEx/pages/j48yqHrYfv39cNFAHNej" %}
[Tenants](/administration/settings/tenants.md)
{% endcontent-ref %}

{% content-ref url="/spaces/cNVX03KZzmrGwJihLiEx/pages/Zyn32QzPx6qiUOfPrYRA" %}
[Broken mention](broken://spaces/cNVX03KZzmrGwJihLiEx/pages/Zyn32QzPx6qiUOfPrYRA)
{% endcontent-ref %}

{% content-ref url="/spaces/cNVX03KZzmrGwJihLiEx/pages/-MZBtB6mVs\_9AWRBvBZ-" %}
[Settings](/administration/settings.md)
{% endcontent-ref %}


---

# 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://help.openloyalty.io/technical-guide/getting-started-guide/member-registartion-configuration.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.