---
title: "Permissions"
slug: "permissions"
description: "Learn about permission types in Zilliant CPQ."
tags: ["CPQ", "Permissions"]
updated: 2025-02-14T17:12:05Z
published: 2025-02-14T17:12:05Z
canonical: "docs.zilliant.com/permissions"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zilliant.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Permissions

Zilliant CPQ divides permissions into two types:

- **Static**—Load when a user signs in to the system. CPQ applies static permissions with each REST call the user makes. Define static permissions at the role level.
- **Dynamic**—Restrictions applied to granted permissions at runtime. For example, if a user has the **DeleteQuotePermission**, you can use a dynamic restriction to restrict them from performing this operation.

Define dynamic restrictions at the user or user role level. Each restriction is defined for a specific permission.

In addition, each condition has a business type to which the restriction applies. Supported business types for restrictions are:
  - Quote
  - Sales Item

#### List of permissions

Available permissions defined in the application schema are:

- ALL PERMISSION
  - ADMIN PERMISSION
  - FLINT PERMISSION
  - CREATE PERMISSION
    - CREATE QUOTE PERMISSION (applies to quotes and agreements under negotiation)
      - CREATE LINE ITEM PERMISSION (applies to quotes and agreements)
    - CREATE ACCOUNT PERMISSION
    - CREATE OPPORTUNITY PERMISSION
  - READ PERMISSION
  - UPDATE PERMISSION
    - UPDATE QUOTE PERMISSION (applies to quotes and agreements under negotiation)
    - UPDATE QUOTE STATUS PERMISSION (applies to quotes and agreements under negotiation)
      - UPDATE LINE ITEM PERMISSION (applies to quotes and agreements)
    - UPDATE ACCOUNT PERMISSION
    - UPDATE OPPORTUNITY PERMISSION
  - DELETE PERMISSION
    - DELETE QUOTE PERMISSION (applies to quotes and agreements)
      - DELETE LINE ITEM PERMISSION (applies to quotes and agreements)
    - DELETE ACCOUNT PERMISSION
    - DELETE OPPORTUNITY PERMISSION
  - PUBLISH AGREEMENT PERMISSION
  - DE-ACTIVATE AGREEMENT PERMISSION
  - REVISE AGREEMENT PERMISSION

As shown in the following hierarchy illustration, lower-level permissions are inherited.

![Hierarchy of CPQ permissions](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/Permissions_hierarchy.png?sv=2026-02-06&spr=https&st=2026-10-28T20%3A31%3A18Z&se=2026-10-28T21%3A31%3A18Z&sr=c&sp=r&sig=YO%2FCfBJjxKtNH2M3ZjHFozFR2mLrIeUUmeIgvTdrw68%3D)

For example, users granted the higher-level CREATE PERMISSION inherit the permissions to create quotes, line items, accounts, and opportunities.

The system checks permissions with each REST/Service call.

For details on assigning permissions to users, read **Define permissions for a role** in [Role management](/v1/docs/role-management).