> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/overview/tutorials/releases/create-a-group-pipeline.md).

# Create a group pipeline

Use this tutorial to standardize releases for one app group.

### Before you start

* You need the **Group Administrator** role for the target group.
* Group pipeline management must be enabled.
* The target app group must already exist.

{% stepper %}
{% step %}

### Open pipeline management

Go to [Administration → Pipelines](/administration/pipelines.md).

Choose the group pipeline library.
{% endstep %}

{% step %}

### Select the group

Open the group you manage.

Create a new pipeline in that scope.
{% endstep %}

{% step %}

### Add the release flow

Configure scheduling and versioning.

Then add the steps the group needs for builds, approvals, and deployments.
{% endstep %}

{% step %}

### Test the pipeline

Use one app from the group to create a release.

Confirm the pipeline appears in the group library and runs as expected.
{% endstep %}
{% endstepper %}

### Next steps

* [Create a release](/overview/tutorials/releases/create-a-release.md)
* [Create a group policy](/overview/tutorials/policies/create-a-group-policy.md)
* [Create and assign a group task](/overview/tutorials/tasks/create-and-assign-a-group-task.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bluestorm.io/overview/tutorials/releases/create-a-group-pipeline.md?ask=<question>&goal=<user_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.