> 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/administration/enable-delegated-pipeline-management.md).

# Enable delegated pipeline management

Use this tutorial to let group or app administrators create pipelines.

### Before you start

* You need the **Platform Administrator** role.
* Release management must already be enabled.

{% stepper %}
{% step %}

### Open system configuration

Go to [Administration → System → System Configuration](/administration/system/system-configuration.md).
{% endstep %}

{% step %}

### Open feature settings

Go to the **Feature Settings** tab.

Find the **Release Management** settings.
{% endstep %}

{% step %}

### Enable delegation

Turn on **Group admins can manage pipelines** when group admins should create group or app pipelines.

Turn on **App admins can manage pipelines** when app admins should create app pipelines.
{% endstep %}

{% step %}

### Validate the new permissions

Ask the target administrators to open [Pipelines](/administration/pipelines.md).

Confirm the expected pipeline libraries are now editable.
{% endstep %}
{% endstepper %}

### Next steps

* [Create a global pipeline](/overview/tutorials/releases/create-a-global-pipeline.md)
* [Create a group pipeline](/overview/tutorials/releases/create-a-group-pipeline.md)
* [Create a release](/overview/tutorials/releases/create-a-release.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/administration/enable-delegated-pipeline-management.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.