> 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/content-to-lock/blogs-articles.md).
# Blogs and articles
Lock an entire blog or specific articles within it behind access rules.
The **Blogs** content type locks blog content — either an entire blog, so every post inside it is protected, or specific individual articles, so the rest of that blog stays public.
## Create the lock
1. Open **Locks** in the app's navigation.
2. Click **Create lock**.
3. Give the lock a descriptive name, for example "Members-only blog posts."
## Choose Blogs as the content to lock
4. On the **Lock setup** tab, in the content picker, select **Blogs**.
Select Blogs in the content picker to protect blog content.
5. Choose whether to lock the whole blog or specific articles:
* **Blog** — locks every existing and future article inside the blog you select.
* **Articles** — locks only the specific articles you choose, leaving the rest of the blog public.
Choose between locking a whole blog or selecting specific articles inside it.
6. Depending on your choice, select the blog or the individual articles you want to lock.
{% hint style="warning" %}
Locking blogs and articles may require a paid plan depending on your current plan.
{% endhint %}
7. Click the **Unlock rules** tab to continue.
## Add an access rule
8. Add at least one rule — for example, **Subscribe to unlock**, so visitors must subscribe with their email before reading a locked article.
9. Configure the rule's settings. See [Access rules overview](/b2b-lock-password-protect/access-rules/overview.md) for the full catalogue of available rules.
10. Add every required condition to the access key. All conditions must be satisfied. See [Combining rules](/b2b-lock-password-protect/access-rules/combining-rules.md).
## Choose a lock behavior
On the same **Unlock rules** tab, the right-hand sidebar has a **Blocked visitor behavior** panel — configure it alongside your rule:
11. A locked blog post typically shows a full lock screen in place of the article content until the visitor passes. You can also hide locked articles from your storefront's on-site search and sitemap. Review [Lock behavior overview](/b2b-lock-password-protect/lock-behavior/overview.md) for the full set of options.
## Save
12. Click **Save**. The lock takes effect on your storefront as soon as the app embed is enabled.
## Related docs
* [Access rules overview](/b2b-lock-password-protect/access-rules/overview.md)
* [Lock behavior overview](/b2b-lock-password-protect/lock-behavior/overview.md)
* [Manage locks](/b2b-lock-password-protect/locks/manage-locks.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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.samita.io/b2b-lock-password-protect/content-to-lock/blogs-articles.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.
