> For the complete documentation index, see [llms.txt](https://help.fluorescent.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fluorescent.co/spark/product-pages/product-page-blocks/security-accordion.md).

# Security accordion

{% hint style="info" %}
This feature was added in v5.0.0 on April 12, 2022. See our [changelog](/spark/readme/changelog.md) and [theme update guide](/spark/general/theme-updates.md) to learn more.
{% endhint %}

In the Product template, you can add a **Security accordion** to let customers know how your store ensures the security of their information and transactions.

> See also the [Shipping block](/spark/product-pages/product-page-blocks/shipping-accordion.md) and [Payment block.](/spark/product-pages/product-page-blocks/payment-accordion.md)

## **Set up security block**

Follow the steps to add a security feature block and customize the layout and headings.

{% hint style="warning" %}
Editing a template changes all pages that use that template. To edit specific pages, you can [create and assign new templates](/spark/general/editing-themes/using-templates.md#create-and-assign-multiple-templates) or [insert dynamic content using metafields](/spark/general/adapting-your-theme/dynamic-content-with-metafields.md).
{% endhint %}

<details>

<summary><mark style="color:blue;">STEPS</mark></summary>

In your theme editor (**Customize**):

1. Choose the **Products** template you want to edit.
2. Under the **Product overview** section, click on the **Security** block to open the settings.

   > Or click **(+) Add block** and select **Security accordion**.
3. Choose to display the accordion in the *Left* or *Right* **Column**.

   > The *Left* column sits below your product media. The *Right* column sits below your product form.
4. Set the **Style** of the accordion to be **Open** or **Closed** when customers first visit your product page.
5. (*Optional*.) Change the **Icon** next to the title of your accordion or set it to *None*.

   ![](/files/nGtireaAmS6ThJSKYhBZ)
6. Change the **Title** text to display as the heading that will reveal the content when clicked on.
7. Change the **Text** content to tell customers more about your product or store.

   > Use the formatting buttons to add bold, italics, or links.

   > To show different text on different product pages, you can create new templates or insert dynamic content with metafields..
8. (*Optional*.) Click and hold the drag handles **`⋮⋮`** to rearrange the blocks:

   ![](/files/4UW6Ll3A75SP9Arnc5aO)

   > Click **Remove block** in the block settings to delete a block.

   > Click the **Eye icon** to hide or unhide a block.
9. Click **Save**.

</details>

<br>

***

> **Related links**
>
> [Product template](/spark/product-pages/product-template.md)\
> [Payment accordion](/spark/product-pages/product-page-blocks/payment-accordion.md)\
> [Shipping accordion](/spark/product-pages/product-page-blocks/shipping-accordion.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 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://help.fluorescent.co/spark/product-pages/product-page-blocks/security-accordion.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.
