> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/armor/access-control/permission-sets.md).

# Permission Sets

This document explains how to create a new Permission Set in the DuploCloud AI Suite Access Control panel.

***

## Prerequisites

* Access to the DuploCloud AI Suite admin panel
* Admin permissions on the Access Control section

***

## Step 1 — Navigate to Access Control

Go to **AI Admin → Access Control** in the left-hand navigation. The page opens on the **Permissions** tab by default, which lists all existing permission sets.

![Step 1 — Permissions tab](/files/PguhaCuXF32jgKdzwoai)

***

## Step 2 — Click "Add"

In the top-right corner, click the **+ Add** button. The Add Permission Set form slides in.

![Step 2 — Add Permission Set form](/files/KtrubaBsxy0AMgo0vLdt)

***

## Step 3 — Enter a Name

Click the **Name** field and type a name for the permission set.

In this example: `QA-Test-Permission-Set`

![Step 3 — Name filled](/files/NRC5MJOHygGgNb8382Ls)

***

## Step 4 — Enter a Description

Click the **Description** textarea and describe the purpose of this permission set.

![Step 4 — Description filled](/files/7rMdz5KjA7c5UekG1Bcj)

***

## Step 5 — Open the Workspace Permission Modal

Click **+ Add Workspace Permission**. A modal dialog opens with fields for:

| Field          | Purpose                                          |
| -------------- | ------------------------------------------------ |
| Workspace      | The workspace this permission applies to         |
| Allowed Scopes | Resources the user can access                    |
| Denied Scopes  | Resources explicitly blocked                     |
| Allowed Agents | AI agents the user can use (empty = all allowed) |
| Denied Agents  | AI agents explicitly blocked                     |

![Step 5 — Add Workspace Permission modal](/files/zQbu4yqZHnxY3hj3nxZR)

***

## Step 6 — Select the Workspace

Click the **Workspace** dropdown and select the target workspace.

In this example: `Production-DevOps`

![Step 6 — Workspace selected](/files/lzdE6VAWeBAYe2YCMKPJ)

***

## Step 7 — Select Allowed Scopes

Click the **Allowed Scopes** dropdown and select the scopes to grant access to. You can select multiple.

In this example: `jira` and `aws-prod-scope`

![Step 7 — Scopes selected](/files/vLOTuQQOvloBl0YDr1Lf)

***

## Step 8 — Allow All Agents

Leave the **Allowed Agents** field empty to allow access to all agents. No selection is required.

![Step 8 — Agents left empty (all allowed)](/files/vLOTuQQOvloBl0YDr1Lf)

***

## Step 9 — Confirm the Workspace Permission

Click the **Add** button inside the modal to save the workspace permission entry.

![Step 9 — Workspace permission added](/files/qk2U71Wp0V2744YM5LBu)

***

## Step 10 — Submit the Form

Review the completed permission set form, then click **Create Permission Set**.

![Step 10 — Before submit](/files/nBLVdXBc1uQtWbw8BZaq)

A green **Success** toast confirms the permission set was saved.

![Step 11 — After submit](/files/78Tdsi4zYh63GGfGDvji)

***

## Step 11 — Verify in the List

The new permission set appears at the top of the Permissions table with the associated workspace.

![Step 12 — Final permissions list](/files/78Tdsi4zYh63GGfGDvji)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.duplocloud.com/docs/armor/access-control/permission-sets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.