{"section":"troubleshooting","requestedLocale":"en","requestedSlug":"logged-out-users-see-information-in-my-store-with-access-restriction","locale":"en","slug":"logged-out-users-see-information-in-my-store-with-access-restriction","path":"docs/en/troubleshooting/integrations-and-channels/logged-out-users-see-information-in-my-store-with-access-restriction.md","branch":"main","content":"Your brand main account website should have restricted access, but logged-out users see products and information from a sales channel without access restriction. This issue can occur when a [white label seller](/en/docs/tutorials/white-label-seller), such as a [franchise account](/en/docs/tutorials/what-is-a-franchise-account), fulfills orders from one of your store websites, such as a [multistore](/en/docs/tutorials/managing-a-multistore) website.\n\n## Cause\n\nFor a white label seller to fulfill orders for your store, the sales channel it serves must be eligible in the [binding](/en/docs/tutorials/how-the-relationship-between-websites-and-business-policies-works#eligibility-rule) of the **main account**, even if the seller only delivers orders from another website. Being eligible in the binding means that the sales channel is selected in the binding configuration of the main account website, allowing that website to render information for that sales channel.\n\nWhen the main account sales channel has access restriction, as in B2B operations, this rule combines with the [exception to the priority rule](/en/docs/tutorials/how-the-relationship-between-websites-and-business-policies-works#exception-to-the-priority-rule): If a sales channel with access restriction is above an eligible sales channel without restriction, the rendered sales channel is the one without restriction. As a result, logged-out users see the main account website with the information of the sales channel without access restriction, which was originally intended for another website.\n\n### Example\n\nConsider a brand with the following architecture:\n\n- **Main account website:** Sales channel A (with access restriction). Only sales channel A is eligible in the binding of this website, and it has its own inventory.\n- **Multistore website:** Sales channel B (without access restriction). Only sales channel B is eligible in the binding of this website. The catalog is shared with the main account. Sales channel B has no access restriction because, in this example, it serves an additional B2C website that must be accessible to logged-out users.\n- **White label seller:** Franchise account that only fulfills orders placed in sales channel B.\n\nFor the white label seller to deliver the multistore orders, sales channel B must also be eligible in the binding of the main account. The following diagram illustrates this architecture:\n\n```mermaid\nflowchart LR\n    subgraph main[\"Main account website\"]\n        direction TB\n        A[\"Sales channel A<br/>(with access restriction)\"]\n        B1[\"Sales channel B<br/>(without access restriction)\"]\n    end\n\n    subgraph multistore[\"Multistore website (B2C)\"]\n        B2[\"Sales channel B<br/>(without access restriction)\"]\n    end\n\n    SWL[\"White label seller<br/>(franchise account)\"]\n\n    B2 -- \"orders placed in sales channel B\" --> SWL\n    SWL -. \"fulfills sales channel B orders\" .-> B1\n```\n\nThe sales channel order is configured as follows:\n\n1. Sales channel A (with access restriction)\n2. Sales channel B (without access restriction)\n\nBased on the priority rule, the main account website would render sales channel A, which is at the top of the order. However, sales channel A has access restriction, and sales channel B, which is below it, doesn't. In this case, the exception to the priority rule applies. As a result, logged-out users, who don't meet the access conditions of sales channel A, see the main account website with the information of sales channel B.\n\n## Solution\n\nTo prevent logged-out users from seeing the information of sales channel B on the main account website, follow the steps below. You'll create a sales channel without products and place it before sales channel B in the order.\n\n1. [Create a sales channel](/en/docs/tutorials/creating-a-trade-policy) C, without access restriction.\n2. Make sales channel C eligible in the binding of the main account. Learn how in **step 8** of the article [Linking a store to a folder structure in CMS (binding)](/en/docs/tutorials/linking-an-account-name-to-a-website-binding).\n3. In the VTEX Admin, go to **Store Settings > Channels > Sales Channels**.\n4. In the **Position** column, set sales channel C to a position before sales channel B.\n\n> ⚠️ Don't make products available for sales channel C. It must remain without products so that the main account website doesn't display information to logged-out users.\n\nWith this configuration, the sales channel order is as follows:\n\n1. Sales channel A (with access restriction)\n2. Sales channel C (without access restriction and without products)\n3. Sales channel B (without access restriction)\n\nThe following diagram illustrates this configuration. Sales channel C is eligible in the binding of the main account, between sales channel A and sales channel B, and has no products:\n\n```mermaid\nflowchart LR\n    subgraph main[\"Main account website\"]\n        direction TB\n        A[\"Sales channel A<br/>(with access restriction)\"]\n        C[\"Sales channel C<br/>(without access restriction<br/>and without products)\"]\n        B1[\"Sales channel B<br/>(without access restriction)\"]\n    end\n\n    subgraph multistore[\"Multistore website (B2C)\"]\n        B2[\"Sales channel B<br/>(without access restriction)\"]\n    end\n\n    SWL[\"White label seller<br/>(franchise account)\"]\n\n    B2 -- \"orders placed in sales channel B\" --> SWL\n    SWL -. \"fulfills sales channel B orders\" .-> B1\n```\n\nThis way, logged-out users access the main account website without products, because sales channel C (without access restriction) is rendered.\n\nSales channel B remains eligible in this binding so that the white label seller can fulfill the multistore orders. It isn't rendered because it's below sales channel C in the order.\n\nAfter logging in, users who meet the access restriction conditions see the products with the information of sales channel A."}