> For the complete documentation index, see [llms.txt](https://docs.b2b-sellers.com/b2b-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2b-sellers.com/b2b-platform/user-documentation/admin-settings-configuration/url-authentication.md).

# URL Authentication

Login via URL Hash | Technical Pluginname: B2bUrlAuthentication

With the help of the URL authentication plugin there is a simplified possibility for the different user groups to login.

### **Functionality** <a href="#functionality" id="functionality"></a>

The store URL is extended by the user's e-mail address and an individual hash.

The hash is stored in the backend for the user groups customers, buyers and sales staff. The overall URL can be copied from the B2B platform's account management and saved for example in the browser's favorites.

#### Structure of the URL <a href="#structure-of-the-url" id="structure-of-the-url"></a>

<figure><img src="https://2179115665-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2AzVR8ntudi7m6tGzlV7%2Fuploads%2FqU6qoBkNdOCny4HFSzrg%2Fimage.png?alt=media&amp;token=a2dab35d-efb5-442c-a5fc-ad1512f81c57" alt=""><figcaption></figcaption></figure>

#### Enable URL authentication <a href="#enable-url-authentication" id="enable-url-authentication"></a>

1. Navigate to the Account tab in the B2B platform.
2. Activate the slide bar "Yes, I want a custom login link".

#### **Do you want URL authentication also for sales employees or for private customers?** <a href="#do-you-want-url-authentication-also-for-sales-employees-or-for-private-customers" id="do-you-want-url-authentication-also-for-sales-employees-or-for-private-customers"></a>

You can store the hash for the entity "employee" and "customer". This also means that you can store a hash for sales employees or private customers in the Shopware Administration and they can then also log in via link.

Navigate in the Shopware Administration to "Customers > Overview".

1. Click on "Edit" to be able to edit the corresponding user.
2. Scroll down the "General" tab to "Custom fields".
3. Enter the "Hash for URL authentication" and click on "Save".

<figure><img src="https://2179115665-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2AzVR8ntudi7m6tGzlV7%2Fuploads%2FDdlhame4wbEyLUPsdtAO%2Fimage.png?alt=media&amp;token=b066f1a5-1741-4d5d-97a3-97542460737e" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Note Alert: Please enter a secure hash of at least 25 characters. Please do not use umlauts.
{% endhint %}


---

# 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.b2b-sellers.com/b2b-platform/user-documentation/admin-settings-configuration/url-authentication.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.