Workspaces

A workspace is your isolated “build room” inside AutoRABIT (ARM). Whenever you run an operation that needs local disk—such as EZ-Commit, a merge or a CI job—ARM spins up (or re-uses) a workspace linked to the repo/branch in question. That keeps files, temporary build artifacts, and logs separated per operation, so one task never overwrites another.

---

What Is a Workspace?

Think of a workspace as a containerized file system:

• It’s created (or re-attached) automatically when you start a commit, merge, or CI task.

• Multiple workspaces can exist side-by-side—one per concurrent job.

• If a matching workspace already exists, the new job re-uses it to save spin-up time.

---

Workspace Storage

• Every tenant receives 500 GB of workspace capacity.

• ARM emails admins when usage approaches the limit.

• Once the cap is hit, no new jobs can start until you increase the limit or delete idle workspaces.

---

Managing a Workspace

Only Org Administrators can view, reset, or delete workspaces.

Viewing the Workspace List

1. Log in to ARM.

2. Go to Admin › Workspaces.

   
3. The list shows every workspace ever created:

   

   Field	Description
   Label	Workspace name (auto-generated)
   Created On	Timestamp of first creation
   Author	User who owns the workspace
   Repo / Branch	Git location tied to the workspace
   Status	Running or Idle
   Module	ARM feature that created it (EZ-Commit, CI Job, etc.)
   Last Used / Size	Date of last activity and storage consumed

---

Resetting a Workspace

Reset wipes the folder contents but keeps the workspace record.

1. Find the workspace and click Reset.

2. Confirm to restore default state.

   

---

Deleting a Workspace

Delete removes the workspace permanently (repositories remain intact).

1. Click the trash-can icon next to the workspace.

2. Confirm twice—you cannot undo this.

   

   

If the Delete button is missing, your role lacks the required permission.

If the Delete button is grayed out, see the FAQ below.

---

Bulk-Deleting Inactive Workspaces

Free up space by purging all workspaces idle since a given date.

1. Click Settings.

   
2. Choose the cutoff date and confirm.

   

---

Workspace Configurations

Need more space? An Org Admin can request an increase.

• Super Admin logs in and opens Workspace Mgmt.

• Raise the tenant limit—maximum 1 TB (1000 GB)—based on subscription.

Once approved, the new cap takes effect instantly and users can resume jobs without deleting old workspaces.

---

Best Practices

• Clean up idle workspaces weekly to avoid hitting the limit.

• Reset instead of Delete if you just want a fresh working directory.

• Monitor the Last Used / Size column to spot abandoned, space-hogging workspaces early.

---

FAQ

Why am I unable to delete certain workspaces?

Despite having admin privileges in your instance, you are unable to delete certain workspaces, as the Delete button appears grayed out, as shown in the screenshot below.

Base Workspaces

The reason the Delete button is grayed out is that these workspaces are classified as Base Workspaces. Base workspaces are directly linked to a branch in your instance, and they cannot be deleted unless the associated branch is unregistered from AutoRABIT. When you register a new branch, a workspace is created, and they are tightly connected.

If you still wish to remove any workspace where the delete option is grayed out, please ensure that the related branch is no longer needed, and proceed to unregister the branch. Once the branch is unregistered, you will be able to delete the associated workspace.