> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/global-settings/user-management/flosum-cloud-app-permissions/devops-permissions.md).

# DevOps Permissions

## ![](https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FSxcnKlaJKPzDqONWoDNv%2FSummary2-Small-Icon.svg?alt=media\&token=5e3253d0-a069-4ba5-9c06-83c70bd0b21d) Overview

This article explains the DevOps app permissions and how they control access to features. When you create a Role with DevOps permissions, three categories control user access: **Licenses**, **Common Permissions**, and **Organization Permissions**. Each category is explained in the sections below.

### Licenses

The Licenses option sets high-level access to DevOps using the following options:

<table><thead><tr><th width="280">License</th><th>Description</th></tr></thead><tbody><tr><td><strong>Full access</strong></td><td>All Common Permissions and Organization Permissions are available for selection.</td></tr><tr><td><strong>Read access</strong></td><td>Common Permissions are restricted to <strong>Pipeline executions</strong> and <strong>Read (View only)</strong>, and no Organization Permissions are available.</td></tr></tbody></table>

### Common Permissions

Common Permissions control access to the Pipelines and Pull Requests features. The following tables describe the available permissions.

**Pipelines**

<table><thead><tr><th width="280">Permission</th><th>Description</th></tr></thead><tbody><tr><td><strong>Pipeline executions</strong></td><td>Allows users to execute pipelines only.</td></tr><tr><td><strong>Manage &#x26; Execute pipelines</strong></td><td>Allows users to create, edit, and execute pipelines.</td></tr></tbody></table>

**Pull Requests**

<table><thead><tr><th width="280">Permission</th><th>Description</th></tr></thead><tbody><tr><td><strong>Read (View only)</strong></td><td>Allows users to view pull requests only.</td></tr><tr><td><strong>Contribute (Create and Comment)</strong></td><td>Allows users to create pull requests, request review, request changes, approve, and merge.</td></tr></tbody></table>

### Organization Permissions

Organization Permissions control access to actions for specific organizations. You add organizations individually and select actions for each one. The table below describes each permission.

<table><thead><tr><th width="279.99993896484375">Permission</th><th>Description</th></tr></thead><tbody><tr><td><strong>Retrieve</strong></td><td>Allows users to retrieve metadata from the org and add components from the org to a branch.</td></tr><tr><td><strong>Validate</strong></td><td>Allows users to run a validation task for the org.</td></tr><tr><td><strong>Deploy</strong></td><td>Allows users to deploy a branch to the org.</td></tr></tbody></table>


---

# 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.flosum.com/global-settings/user-management/flosum-cloud-app-permissions/devops-permissions.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.