Maintaining your workspaces: modify, suspend, delete

01In a nutshell #sec_f8f3efcf

A workspace is created in nine steps and is then governed from the list — where the committing gestures are Suspend and Activate, and where Delete is almost always the wrong answer in an audit product.

02Where #sec_cb2b77bc

Workspaces, in the navigation. One line per workspace: its status (Active, Suspended), its solutions and workloads, its policies, its features (all five, N out of 5, or none), its active campaigns, its last update. A search, and filters by solution and by policy.

A suspended workspace still exists, it is only filtered: if a line is missing, check the filters before looking elsewhere.

Two signals on a line are worth an action: Incomplete Boundary, and No tenant — nothing is collected or Inactive Tenant. A workspace in this state sees nothing.

03Modify #sec_13e9d26f

Modify reopens the wizard on its steps — the same as at creation, described in Onboarding a workspace:

1. Identity — name, description, time zone (*all workspace deadlines are

calculated in this time zone*), working days and time range.

1. Solutions & workloads — what the workspace will certify.
2. Policies — the playable policies.
3. Boundary, tenant by tenant — data locations, domains.
4. Attribute filters — a readable restriction *from left to right, without

precedence*.

1. Features — Carbon Score, Remediation, Sanctuary, Delegation, and the

RITA mode: this choice decides whether the workspace data is sent to an AI model — not the assistant's capacity. The workspace can only go below the subscription ceiling.

1. Roles — read-only: roles are managed in the Roles screen, the

next page.

1. Credits — the reserved envelope.
2. Summary.

Two things are not modified here, and the wizard says so. The service status is not edited here: Suspend and Activate are gestures from the workspace list. And shrinking the boundary of a workspace that has ongoing requests is refused: Shrinking what this workspace collects would leave issued requests pointing to objects that nothing collects anymore. Close or wait.

04The credit envelope #sec_88dbccbc

At the Credits step, the subscription is displayed in four parts: Already promised, This workspace, Free to promise, and if applicable Overcommitted. These credits are reserved for this workspace: no other can consume them. What is not allocated remains available to the subscription.

Zero is a legitimate choice: the workspace exists, it simply does not arm any campaign as long as it is not endowed. And overcommitment is a warning to be taken seriously: the last workspaces to arm a campaign would find nothing.

05Suspend #sec_29b47bc6

The gesture from the list. The dialog says exactly what happens: Access to the Workspace Center closes and roles can no longer be assigned. Nothing is deleted — reactivation finds everything as is.

An option: Suspend campaigns as well — freezes reminders, escalations, and deadlines until reactivation; no new cycle will arm. Reviewers can still decide on pending requests. Without it, campaigns continue while the workspace console is closed. Check it unless there is a contrary reason.

06Reactivate #sec_8b0c0ff7

Activate reopens access and assignments. Two guards may refuse:

• *This workspace has no active boundary: nothing feeds it. Define a boundary*

before activating it.*

• *Activation refused: this workspace no longer has any role that holds — assign one*

first.* A workspace without an active manager is not a workspace.

07Delete, and why you will almost never do it #sec_c19290d5

Delete places the workspace in Deleted Items, suspended, restorable until … — then purged for good. The dialog lists what is frozen with it: the campaigns still in progress, and the envelope of N credits that only returns to the subscription upon its purge.

Then the sentence to remember: Nothing is destroyed today. After the …, the purge is final: campaigns, occurrences, and roles leave with it, and its credits return to the reservoir. In an audit product, suspending is almost always the best answer. The Suspend button instead is there for that. To arm the deletion, you must enter the name of the workspace.

When review pieces depend on it, deletion is refused: Suspending the workspace preserves everything and stops everything.

08What a workspace cannot become #sec_dd67505e

The subscription allows a maximum number of workspaces; reached, creating another is refused. And a workspace governs the workloads of a solution: the solutions come from the subscription contract — if one is missing, it is a matter of contract, not a setting you missed.

09To remember #sec_b0c579cb

Modify to adjust, suspend to stop, reactivate when teams are ready. Delete is just a suspension with a purge date, and the product will tell you this every time. What keeps a workspace standing are its roles — the next page.