> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/b2b-lock-password-protect/help/contact-support.md).

# Contact support

How to reach the Sami B2B Lock, Password Protect support team when self-service troubleshooting isn't enough.

If the [FAQ](/b2b-lock-password-protect/help/faq.md) and [Lock not working](/b2b-lock-password-protect/help/lock-not-working.md) checklist haven't solved your issue, reach out and the team will help directly.

## Email

Email **<support@samita.io>** with a description of the problem, the lock (or setting) involved, and — if it's a storefront issue — a link to the page where you're seeing it. The more specific you can be about what you expected versus what happened, the faster support can help.

## In-app Contact form

You can also reach the team from inside the app on the **Contact us** page in the app's navigation. It's a short form with:

* **Your name** and **Your Email** — pre-filled from your store's info where available.
* **Subject** — pre-filled with a default subject you can edit.
* **Collaborator request code** (optional) — see below.
* **Message** — describe your issue or question.

Fill in the fields and click **Send** to submit your message directly to support.

### Giving support access to your store

The page explains that support can help faster with access to your Shopify admin — specifically **Apps** and **Online store → Themes** — and gives you the email address to use when creating a staff account for them.

If you'd rather grant access as a collaborator, the form has a **Collaborator request code** field. Your 4-digit code is in your Shopify admin under **Settings → Users and permissions**, in the **Collaborators** section; there's also a **get collaborator code** shortcut next to the field.

{% hint style="info" %}
Granting access is optional. You can submit the form without it — support will just ask for whatever they need to reproduce the issue instead.
{% endhint %}

<figure><img src="https://27754559-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF4qMYopXntYz9YgUqZSo%2Fuploads%2Fgit-blob-2764ed8b8c2fc4fe084296d08b5f589519130c4a%2Fscreenshot-contact-support-form.png?alt=media" alt="The app&#x27;s in-app Contact us page showing the name, email, subject, and message fields"><figcaption><p>The in-app Contact us form, reachable from the app's main navigation.</p></figcaption></figure>

{% hint style="info" %}
Try the self-service steps first — many issues (an app embed that's off, a leftover grant-access cookie, a fail-open Custom liquid rule) can be confirmed and fixed in a couple of minutes without waiting on a reply.
{% endhint %}

## Related docs

* [FAQ](/b2b-lock-password-protect/help/faq.md)
* [Lock not working](/b2b-lock-password-protect/help/lock-not-working.md)
* [Enable the app embed](/b2b-lock-password-protect/quick-start/enable-app-embed.md)


---

# 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.samita.io/b2b-lock-password-protect/help/contact-support.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.
