Recycle Bin

The Recycle Bin stores snapshots of deleted resources such as browser environments, proxy configs, user groups, and extensions so you can restore them in case of accidental deletion or later need.

📌 Before you use it

• The Recycle Bin is a safety net, not long-term storage. Records may be cleaned automatically according to system policy after expiry.
• Restore operations write data back into the corresponding business module. Make sure restored configs do not conflict with existing data.
• “Delete permanently” and “Batch delete permanently” are irreversible. Double-check before confirming.

🚪 Entry

• Use the left navigation to open the “Recycle Bin” page.
• The top area is for filters and batch actions; the bottom is the list and pagination.
• Accounts without permission will see a “No permission” message; an admin must grant the proper rights.

🧭 Supported data types

Use the segmented control at the top to switch source types:

• Browser configs: deleted browser environments (Environment Management).
• Proxy configs: deleted records from Proxy Management.
• User group configs: deleted team groups.
• User extensions: deleted user extension apps.
• Team members: deleted team users.
• All: view all recycled data.

When you switch type, the list reloads according to current filter settings.

⚡ Quickstart: Restore accidentally deleted data

Step 1｜Choose source type
In the segmented control, choose the corresponding source. For example, if you deleted a browser environment, choose “Browser configs”.

Step 2｜Locate the record
Use “Deleted time”, “Source table”, “Deleted by”, etc. to find your target record.
If the list is empty, click “Reset filters” in the empty state to clear filters and reload.

Step 3｜View details (optional)
Click “Details” in the row operations to open the details drawer. It shows the full snapshot, including source table, source data ID, source payload, creator/deleter, etc.

Step 4｜Restore
Click “Restore” in the target row. A confirmation dialog appears:

• If you confirm, the system calls the restore API and writes the data back to the corresponding module.
• On success, you see “Restore succeeded”, and both the Recycle Bin and related module stats refresh.

Step 5｜Verify
Go back to the corresponding page (such as Environment Management or Proxy Management) and confirm the data is present and correct.

🧹 Quickstart: Permanent deletion

Delete a single record permanently

Step 1｜Locate the record
Use source type and list fields to find the record you want to delete permanently.

Step 2｜Click “Delete permanently”
Click “Delete permanently” in the row actions. A confirmation dialog warns that this operation cannot be undone.

Step 3｜Confirm
After confirmation, the system calls the delete API and removes the record from the Recycle Bin permanently.

Batch permanent deletion

Step 1｜Select records
Use the checkboxes on the left to select multiple records.

Step 2｜Click “Batch delete permanently”
Click the “Batch delete permanently” button in the top-right. The dialog shows how many records will be deleted.

Step 3｜Confirm
After confirmation, the system deletes the selected records one by one and refreshes the list.

📋 List fields

• Deleted time: when the record entered the Recycle Bin.
• Source table: business module where the data came from (Environment, Proxy, etc.).
• Expiry time: planned cleanup time for this record. Exact behavior depends on system config.
• Deleted by: user who performed the delete.
• Restored by: user who restored the record (if any).
• Restore time: time of the restore operation (if any).
• Actions:
  • Details: view the full snapshot.
  • Restore: available when not yet restored and not expired.
  • Delete permanently: remove it from the Recycle Bin completely.

🔎 Recycle Bin details drawer

Click “Details” to open the drawer with these main fields:

• Primary ID: unique ID of this recycle record.
• Source table: name of the business table.
• Source data ID: primary key of the original business record.
• Source data: original data as JSON text, supporting line breaks and large payloads for analysis.
• Restored: Yes / No.
• Expiry time: planned auto-cleanup time.
• Created-by ID / Created-by: original creator info.
• Created time: when the original data was created.
• Updated-by ID / Updated-by: last modifier of the original data.
• Updated time: last update time of the original data.
• Deleted flag: whether the record has been physically deleted.

🧩 Recycle strategy & notes

Strategy

• Auto recycle: Delete operations can automatically move records into the Recycle Bin with a retention period, then clean them according to system policy after expiry.
• Manual permanent deletion: Users with permission can manually delete records permanently in the Recycle Bin.
• Restore: You can restore records with their original configuration and data (if they haven’t been overwritten).

Notes

• The Recycle Bin does not keep external dependencies (such as accounts or credentials in a proxy provider’s own dashboard). After restore, you may need to re-bind these in external systems.
• Large resources (for example ones with heavy local cache or many related records) may take longer to restore. Prefer doing such restores during off-peak hours.
• For better auditability, it’s recommended to pair Recycle Bin operations (restore/permanent delete) with Operation Logs, so you can trace who did what and when.