> 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/sami-b2b-onboarding/store-access/store-access.md).

# Store access overview

Choose who can browse and buy in your store, and what visitors who aren't approved see.

Store access decides who can see your products and prices, and who can buy them. In Sami B2B Onboarding, you set it in **Settings › Access**. Only admins can open this section.

## Pick how open your store is

Under **Storefront visibility**, the **Who can browse, who can buy** setting has three options. The other rules on the page depend on which one you pick.

| Option                                           | Browse             | Buy                | Rules you can turn on                                                                                                        |
| ------------------------------------------------ | ------------------ | ------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| **Private wholesale store**                      | Approved companies | Approved companies | The store lock is always on. You can also hide prices and add to cart on the pages the lock leaves open, and block checkout. |
| **Public catalog, private purchasing** (default) | Everyone           | Approved companies | Hide prices, hide add to cart, block checkout and lock the store, each on its own.                                           |
| **Public catalog, public purchasing**            | Everyone           | Everyone           | None. **Test mode**, **Prices and checkout** and **Store lock** are hidden.                                                  |

**Buy: Approved companies** holds only while **Block checkout while pending** is on. That switch is what stops other buyers at checkout.

## Who counts as approved

A visitor is approved when they're logged in to your store and one of these is true:

* They buy for a company in Shopify. They're a contact of that company.
* **B2B approved** is on, on their customer page in Shopify. The app turns it on when you approve their application.

Everyone else isn't approved. That includes guests, and logged-in customers who haven't applied or are still waiting for a decision. Customer tags don't count. The `b2b-approved` tag that the app adds on approval is a label for your own segments, and it doesn't let anyone in.

## How the rules work

* **Hide prices from retail visitors**, **Hide add to cart** and **Whole store lock** change what your storefront shows. They need the app embed. See [Turn on the app embed](/sami-b2b-onboarding/getting-started/turn-on-the-app-embed.md).
* These three rules aren't a security barrier. A visitor who knows how can still find prices in the page code. **Block checkout while pending** is the rule that stops a purchase, because Shopify checks it inside checkout. It doesn't need the app embed. Keep it on whenever you hide prices or lock the store.
* None of the rules apply in the theme editor, so you can still see and design every page. To check a rule, open your storefront in a normal browser window.
* The rules cover your whole storefront, but the store lock always leaves log-in, account and application form pages open. The rules reach the storefront after you click **Save** in the save bar.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Hide prices and add to cart</strong></td><td>Replace prices with a log-in link and remove the buy buttons.</td><td><a href="/sami-b2b-onboarding/store-access/hide-prices-and-add-to-cart.md">Hide prices and add to cart</a></td></tr><tr><td><strong>Lock the store</strong></td><td>Show visitors a screen that asks them to log in or apply.</td><td><a href="/sami-b2b-onboarding/store-access/lock-the-store.md">Lock the store</a></td></tr><tr><td><strong>Block checkout until approved</strong></td><td>Stop anyone who isn't approved from completing an order.</td><td><a href="/sami-b2b-onboarding/store-access/block-checkout-until-approved.md">Block checkout until approved</a></td></tr><tr><td><strong>Ask buyers to log in before applying</strong></td><td>Show guests a log-in prompt instead of the application form.</td><td><a href="/sami-b2b-onboarding/store-access/log-in-before-applying.md">Ask buyers to log in before applying</a></td></tr><tr><td><strong>Test your access rules</strong></td><td>Try the rules on your own account before your buyers see them.</td><td><a href="/sami-b2b-onboarding/store-access/test-mode.md">Test your access rules</a></td></tr></tbody></table>

## Next steps

* [Test your access rules](/sami-b2b-onboarding/store-access/test-mode.md) — turn on test mode first if your store already takes orders.
* [Turn on the app embed](/sami-b2b-onboarding/getting-started/turn-on-the-app-embed.md) — the storefront rules only work with the embed on.
* [Approve an application](/sami-b2b-onboarding/reviewing-applications/approve-an-application.md) — approving a buyer turns on **B2B approved** for them.


---

# 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://docs.samita.io/sami-b2b-onboarding/store-access/store-access.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.