> For the complete documentation index, see [llms.txt](https://www.locksmith.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.locksmith.guide/tutorials/more/locking-the-customer-registration-form.md).

# Locking the customer registration form

{% hint style="danger" %}
**Locking the default registration page with Locksmith will&#x20;*****only*****&#x20;work with Legacy Customer Accounts.**\
\
**The New Customer Account system creates an account as soon as the customer uses the login form, and so registration&#x20;*****cannot*****&#x20;be locked.**\
\
**In that case, we recommend approving customers with account tags instead, after they create an account.**
{% endhint %}

To try this out, open up Locksmith, and start typing "registration", like so:

![](/files/rXa4Kts2T2isArsf0Avb)

Click on the "Customer Registration" result and then click "Save." Locksmith will create a lock that covers your shop's registration page. From there, feel free to add whatever keys you like!

{% hint style="warning" %}
**Hint:** Key conditions based on things like customer tags won't ever allow access because a customer needs to create an account and sign in before they access! If you don't want any customers to register on their own, you can simply leave this lock with no keys. Otherwise, you'll want to use non-customer-account based key conditions such as [passcodes](/keys/passcode-keys.md) or [secret links](/keys/secret-link-keys.md).
{% 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 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://www.locksmith.guide/tutorials/more/locking-the-customer-registration-form.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.
