> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/schlage-lock-interface/configuring-pin-only-function-on-a-schlage-ad-series-reader.md).

# Configuring PIN Only function on a Schlage AD Series Reader

### Introduction

This procedure describes how to configure the "PIN only" function on a Schlage AD Series Reader.

### Procedure

1. Click **Configure** from the menu bar, then **Schedules**.

   The **Schedule** List Window opens.
2. Highlight the Access Zone Schedule to be assigned.
3. Click the **Times** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-305b11f757a1ad4ecf702bc391253e4bb3840447%2Fazschedule_pinonly.png?alt=media)
4. Click on the **State/Action**, and select either the "Code or Card - No PIN" or "Code or Card - PIN" option from the drop-down list.
5. Click the **OK** button.
6. To complete configuration, use one of the methods below as appropriate for your site:

   <table><thead><tr><th width="130">Method</th><th>Description</th></tr></thead><tbody><tr><td>By Access Zone</td><td>This method configures one code that can be shared by anyone who wants to gain access to the system. The disadvantage of this is that there is no way to track who used the code.</td></tr><tr><td>By Cardholder</td><td>This method uses unique codes assigned to Cardholders, so the system can identify who gained access.</td></tr></tbody></table>

#### By Access Zone

1. Click **Configure** from the menu bar, then **Access Zones**.

   The **Access Zone** List Window opens.
2. Highlight the Access Zone to be configured.
3. **Right click** and select **Properties**.
4. Click the **Access Mode** tab.
5. From the **Schedule** drop-down list, select the appropriate Schedule.
6. Enter a user code in the **Code only code** field.

   The example below shows 1122 has been entered as the code.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f67193955ba55264da199cbe0864c40b1f003243%2Fschlage_pinonly1.png?alt=media)
7. Click the **OK** button.

#### By Cardholder

1. Click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens.
2. Highlight the Schlage Door you want to configure the "PIN only" function for.
3. **Right click** and select **Properties**.
4. Click the **Advanced** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8dfb673381a298a58c691e3195d1b0fec841181a%2Fschlage_pinonly2.png?alt=media)
5. Check the **PIN is user code** checkbox, and click the **OK** button.
6. Click **Manage** from the menu bar, then **Cardholders**.

   The **Cardholder** List Window opens.
7. Highlight a Cardholder that requires access via the Schlage Reader.
8. **Right click** and select **Properties**.
9. Click the **User Code** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-80e7c1bc176a56199ae69a1a61666491354f1efd%2Fschlage_pinonly3.png?alt=media)
10. Enter a 4-6 digit user code in the **User code** field.
11. Confirm the user code by re-typing it in the **Confirmation** field.
12. Click the **OK** button.
13. Repeat Steps 7 - 12 for each Cardholder that requires access at the Reader.


---

# 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.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/schlage-lock-interface/configuring-pin-only-function-on-a-schlage-ad-series-reader.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.
