> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-greatstore/configure/security.md).

# Security

**Configure → Security.** Three allowlists controlling where your chat can run and what your custom components may talk to.

<figure><img src="/files/Yi8XBzwHeSsK6uF6RiIM" alt="Configure → Security"><figcaption><p>Configure → Security</p></figcaption></figure>

## Additional embed origins

Other domains where this store's chat is embedded — staging, previews, a second brand site. Each must be a full origin:

The point of the allowlist: your embed runs an LLM **on your credits**. Restricting the origins it works on stops someone embedding your chat on their own site and consuming your usage. Outside the allowed origins, the embed simply errors.

```
https://staging.example.com
```

Without this, the panel will not load on that domain.

## Trusted script hosts

Origins your custom components may load JavaScript from, as a host:

```
cdn.example.com
```

These extend the storefront CSP `script-src` on top of the Greatstore defaults.

## Trusted connect hosts

Origins those scripts and components may `fetch` from or open WebSockets to. Extends `connect-src`; each entry produces both `http(s)` and `ws(s)` variants, so you do not need to add both.

{% hint style="warning" %}
These lists widen your storefront's content security policy. Add only hosts you control or explicitly trust, and remove entries when a component stops using them.
{% endhint %}

## Related

{% content-ref url="/pages/x84J3jdgA2RANWP4yzC8" %}
[Building an app](/maker-greatstore/apps/building-an-app.md)
{% endcontent-ref %}


---

# 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.maker.co/maker-greatstore/configure/security.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.
