> 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:

![](https://277214568-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUeGWHuijBPr8Og1Gta%2Fuploads%2FLPhHQTGalpmJhPd8mcIc%2FScreenshot%202025-01-29%20at%2011.11.23%20AM.png?alt=media\&token=68bc72bc-586f-4702-98de-67ffd369c03f)

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](https://www.locksmith.guide/keys/passcode-keys.md) or [secret links](https://www.locksmith.guide/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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.locksmith.guide/tutorials/more/locking-the-customer-registration-form.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.
