> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bhealthpractice.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Share a protocol link with your client in AnyScript

> How to generate and send a protocol link — including client storefront links, general share links, and the email option on the protocol detail page.

Once a protocol is saved, the next step is getting it in front of your client. AnyScript generates a shareable link that takes your client directly to their supplement plan. From there they can review each product, see any notes you have written, and place an order. You earn commission on every purchase made through that link.

## Two ways to share

The type of link generated depends on whether the assigned client has a personal storefront token:

<CardGroup cols={2}>
  <Card title="Client storefront link" icon="store">
    If your client has a share token, the link opens their personal shop pre-filtered to this protocol. The URL takes the form `/shop/{token}?protocol={id}`. This gives the client a branded, personalised experience.
  </Card>

  <Card title="General share link" icon="link">
    If your client does not yet have a share token, the link goes to a general protocol view page at `/rx/{shareToken}`. The client can still see and purchase the prescribed products.
  </Card>
</CardGroup>

<Info>
  Share tokens are assigned automatically when a client is created. If a client is missing a token, check that their profile is fully set up under **Practice > Clients**.
</Info>

## Copying the link from the protocols list

<Steps>
  <Step title="Open the protocols list">
    Go to **Practice > Protocols**.
  </Step>

  <Step title="Open the row menu">
    Find the protocol you want to share and click the **⋯** (more options) icon on the right side of that row.
  </Step>

  <Step title="Click Share Protocol">
    Select **Share Protocol** from the dropdown. The link is generated and copied to your clipboard immediately.

    A confirmation toast appears: *"Protocol link copied!"* for client storefront links, or *"Link copied!"* for general share links.
  </Step>

  <Step title="Send the link to your client">
    Paste the link into an email, message, or any communication channel you use with the client.
  </Step>
</Steps>

## Copying the link from the protocol detail page

On the protocol detail page, a link icon button sits in the header toolbar next to the email button. Clicking it copies the client storefront link to your clipboard directly.

<Note>
  The link icon button is disabled if the assigned client does not have a share token. In that case, use the **Share Protocol** option from the protocols list to get the general share link instead.
</Note>

## Emailing the protocol to your client

If you prefer to notify your client by email rather than sharing the link manually, you can send a "ready to review" email directly from the protocol detail page.

<Steps>
  <Step title="Open the protocol detail page">
    Click **Manage** on any protocol in the list, or navigate to it directly.
  </Step>

  <Step title="Open the Email tab">
    Click the **Email** tab in the protocol detail view.
  </Step>

  <Step title="Send the email">
    Click **Send email** (or **Re-send email** if you have sent one before). The client receives an email with a private link to their storefront.

    The tab also shows when the protocol was last emailed, so you have a record of outreach.
  </Step>
</Steps>

<Tip>
  You can also trigger the email from the header toolbar using the envelope icon, which opens a confirmation dialog before sending.
</Tip>

## What the client sees

When a client visits their link, they see the SharedScriptView page — a public-facing view of the protocol that shows the prescribed products, your synopsis (if you have written one under the Notes & Synopsis tab), and a checkout flow. The client can purchase directly from this page.

<Warning>
  If you set a protocol to **Inactive**, it will no longer be visible to the client on their storefront. Make sure a replacement protocol is active before deactivating an existing one.
</Warning>