> For the complete documentation index, see [llms.txt](https://docs.frends.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frends.com/bap/general/shop-configuration.md).
# Shop Configuration
Shop settings available to all Organizations.
In this settings page, which you can reach by clicking on "Settings" -> "Shop configuration" (while logged in as a portal admin), you can control settings that are common for all organizations.
Shop configuration view in BAP Settings.
## I**ntegrations available to all organizations**
Templates with the tags listed in this field will be available to all organizations.
## **Categories**
Portal admins can group tags together to form categories, which can be used as filters for searches of templates and processes.
Tags can be categorized in Shop configuration.
Categories configured in Shop configuration.
## **Agent groups to run integrations in**
The test and production agent groups set here will be the default for all organization, if none are selected for the specific organization.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.frends.com/bap/general/shop-configuration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
.png?alt=media&token=0989b7f7-8b85-4841-8bfd-ba763606c188)
.png?alt=media&token=9b5ec3bd-320c-4ced-907e-7853eaeccab7)
.png?alt=media&token=85cefda5-a194-4a99-8f74-576a5c08df7a)