> 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/concepts/workspaces.md).

# Workspaces

This is where it all comes together!

A Workspace is the central entity that ties everything together — attach any number of Scopes and Personas to it. You can create multiple Workspaces and invite users to each one, enabling clear separation of responsibilities across your organization.

Open **Workspaces** from the AI Admin sidebar. Each Workspace appears as a card showing its LLM and scope counts, the Personas attached to it, and when it was last updated. Use the search box and the **Persona**, **Agent**, and **Scope** filters to narrow the list, and the menu on each card to **Edit**, **Delete**, or **View** a Workspace.

<figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-681327536e4cf6b880c7ac72b31d9b6557b244c7%2Fworkspaces-01-list.png?alt=media" alt="Workspaces list with the Add Workspace button highlighted"><figcaption></figcaption></figure>

## Creating a Workspace

1. Click **Add Workspace**. The form is split into steps, listed on the right: **Basic**, one step per provider category under **Providers**, **Prompt**, and **Metadata**.
2. On the **Basic** step, enter:

   * **Name** — must start with a letter and contain only letters, numbers, hyphens, and underscores.
   * **Short Name** (optional) — up to 10 characters. It's used as the prefix for ticket numbers in this Workspace; if you leave it blank, the Name is used with hyphens and underscores removed.
   * **Description** (optional).
   * **Personas** — select at least one.
   * **Analytics ID** (optional).

   Click **Next**.

<figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-f2ead8de59eee7fe01bfdf6467b827de01cbe5f2%2Fworkspaces-02-basic.png?alt=media" alt="Basic step with a name, description, and the devops persona selected"><figcaption></figcaption></figure>

3. Each **Providers** step (**Cloud**, **Kubernetes**, **Observability**, **Incident Management**, **Source Control**, **GRC**, **Sales**, **Marketing**, **Knowledge Base**, **Other**) lists the providers in that category. Expand a provider and select the Scopes to include. A Workspace needs at least one Scope; skip any category you don't need by clicking **Next**.

<figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-04dbf500b5da31edd563ae71697179fdc56e32b0%2Fworkspaces-03-cloud-scopes.png?alt=media" alt="Cloud step with a provider expanded and one scope selected"><figcaption></figcaption></figure>

4. On the **Prompt** step, optionally enter a **System Prompt** (see [Setting a System Prompt](#setting-a-system-prompt)) and add **Prompt Suggestions** or **Prompt Templates**. Each suggestion and template can carry its own Scopes and command execution permissions.

<figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-180e459691f8ff077c89b63cbc662803ff1d7f78%2Fworkspaces-04-prompt.png?alt=media" alt="Prompt step with the System Prompt field filled in"><figcaption></figcaption></figure>

5. On the **Metadata** step, optionally add key/value metadata, then click **Create**.

<figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-4f2c7a090d6bf75eee5f3a73b201f3376799317f%2Fworkspaces-05-metadata.png?alt=media" alt="Metadata step with delete_protection set to false"><figcaption></figcaption></figure>

{% hint style="info" %}
Once a name, at least one Persona, and at least one Scope are set, a **Create** button appears on every step, so you don't have to step through the rest of the form.
{% endhint %}

**Congratulations!** Your Workspace is now ready to receive assignments, interpret goals, break down work, and provide a transparent audit trail—all with human oversight and control.

## Viewing a Workspace

Click a Workspace card to open it. The header shows its description, Short Name, last update, and Workspace ID, and the **Actions** menu has **Edit** and **Delete**.

The **Overview** tab summarizes what's attached: Personas, Scopes, Language models, Knowledge bases, Reports, Incidents, and the creation date.

<figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-7a38fb6466d25446d4f82ba3f66d9fe1fbc4a3d0%2Fworkspaces-06-view-overview.png?alt=media" alt="Workspace detail page on the Overview tab"><figcaption></figcaption></figure>

The other tabs are:

* **Personas** — the Personas attached to the Workspace.
* **System Prompt** — shown only when a System Prompt is set.
* **Secrets** — secrets available to this Workspace's tickets.
* **Audit Trail** — this Workspace's events (administrators only). See [HelpDesk Audit Trail](https://docs.duplocloud.com/docs/concepts/helpdesk/audit-trail.md).
* **Metadata** — the Workspace's key/value metadata.
* One tab per provider category (**Cloud**, **Kubernetes**, and so on) listing the Workspace's Scopes in that category. Click **Add Scope** to attach another Scope. Knowledge Base scopes are attached by sharing a knowledge base with the Workspace, so that tab has no **Add Scope** button.

## Setting a System Prompt

Each Workspace can define a **System Prompt** — free-text instructions injected directly into the agent's system prompt on every ticket in that Workspace.

Enter it in the **System Prompt** field on the **Prompt** step, when you create a Workspace or later from **Edit**. Once saved, it appears on the Workspace's **System Prompt** tab.

<figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-658640088c31c7000c0f09d7a48fc91c8c9a740b%2Fworkspaces-07-view-system-prompt.png?alt=media" alt="System Prompt tab on the Workspace detail page"><figcaption></figcaption></figure>

{% hint style="info" %}
This is distinct from [Agent Memories](https://docs.duplocloud.com/docs/advanced-topics/agent-memories.md). The System Prompt is a single field that's always injected verbatim into every ticket in the workspace. Memory is a set of files the agent reads on demand, and can be turned off per ticket. If the two conflict, persona instructions take precedence over the System Prompt.
{% endhint %}

## Deleting a Workspace

New Workspaces are **delete-protected** by default: they get a `delete_protection` metadata key set to `true`, and **Delete** stays disabled while it is. To delete a Workspace, open its **Metadata** tab, set `delete_protection` to `false` (or remove the key), then choose **Delete** from the **Actions** menu or the card menu. To create a Workspace without protection, add `delete_protection` = `false` on the **Metadata** step, as shown above.

<figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-0e91686053827068beb09d713b806870e0f1702f%2Fworkspaces-08-view-metadata.png?alt=media" alt="Metadata tab showing delete_protection set to false"><figcaption></figcaption></figure>

A Workspace can't be deleted while active projects or incidents still reference it. Deleting a Workspace doesn't delete the Personas or Scopes attached to it — they stay available to other Workspaces.


---

# 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.duplocloud.com/docs/concepts/workspaces.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.
