---
title: "Permissions"
description: "Every permission in the Depot console, what it allows, what it does not, and which role usually carries it."
url: "https://support.outpostplatform.com/reference/permissions/"
product: "depot"
type: "reference"
status: "stub"
ai_summary: "Reference list of Depot console permissions. Permissions are named by area and action, grouped into roles, and checked on the server on every request. One row per permission with what it allows and the roles that hold it by default."
source: "https://gitlab.com/outpostplatform/docs/-/edit/main/src/content/docs/reference/permissions.md"
license: "CC BY 4.0"
---

# Permissions

Every action in the Depot console is gated by a named permission, checked on
the server rather than in the browser. This page lists them so that you can
build a role that gives somebody exactly what their job needs. It is for whoever
administers access.

<!-- TODO: write this page against the reference template.

Sections:

- Scope: which version, and the fact that these are Depot console permissions
  rather than anything to do with your Outpost account.
- How a permission is named, and how to read one you have not seen before.
- The permissions, grouped by area, as one table per area.
- The built in roles, and which permissions each one holds.
- Permissions that are dangerous on their own, and why.
- Permissions that do nothing without another one.
- How a permission change takes effect, and how long a cached decision lives.
- Source: where the catalogue is defined in the product.
-->

Follow the [reference template](https://gitlab.com/outpostplatform/docs/-/blob/main/templates/reference.md).