> 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/keys/more/excluding-content-from-locks.md).
# Excluding content from locks
How to use Locksmith's "always permit" key condition to make sure your some of your content doesn't become locked
This is useful if you have a lock on a collection, but want specific products still available. Or if you have a lock on your "entire store", but want specific pages always accessible.
*It's a quick setup*: you'll actually create a **lock** directly on the content that you want to be unlocked. This can be anything such an entire collection, a product, page, blog, etc.
Once you've added the lock, use the key condition labelled "always permit":
Save the lock, and you're done.
The "lock" that you've just created becomes a sort of anti-lock, so the product, collection, etc that you've placed it one will now always be available.
You may need to create multiple locks like this if you have multiple areas of your store that you would like to remain accessible.
## Related feature: the force open other locks setting
The force open other locks setting is useful if you have multiple locks with overlapping content. This usually means locked collections with some of the same products. If this is you, check out our guide here:
{% content-ref url="/pages/0c8BffnjAyaptBUb4Z8f" %}
[Using the "Force open other locks" setting](/keys/more/using-the-force-open-other-locks-setting.md)
{% endcontent-ref %}
---
# 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/keys/more/excluding-content-from-locks.md?ask=&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.
