Folder Management

Folder Management

Docker and VM configurations are separate, but their folder concepts are intentionally consistent.

Create a folder

1. Open Basic Settings and choose Docker or VMs.
2. Select Add folder.
3. Enter a name unique within the selected parent.
4. Choose an icon or keep the default.
5. Select direct members.
6. Review the preview and save.

Hierarchy and membership

• A folder may be placed beneath another folder using the parent picker.
• The Members tab contains direct container or VM assignments; child folders are separate hierarchy nodes.
• A member should normally have one effective folder.
• Moving a parent keeps its branch together.
• Names must be unique among siblings; the same name may be meaningful in separate branches when no collision exists.
• The maximum hierarchy depth is six levels. Shallow, purpose-driven branches are easier to operate.

Ordering

Manual order uses the six-dot handles and one-step arrow controls. Name/timestamp modes calculate order automatically. Pinned folders are resolved before the selected sort mode. Switch to manual before expecting a drag or arrow operation to define the full order.

Nested pinning promotes the root branch when visible order is calculated; it does not detach the nested folder from its parent.

Available sort modes are Created order, Created newest, Created oldest, Last updated, Manual, Name A–Z, and Name Z–A. Quick filters such as Pinned, Stopped, Empty, No rules, and Has updates change the current Settings view without deleting or reordering data.

On small/touch screens, use Mobile reorder instead of relying on desktop drag behavior. Inline hierarchy undo/redo can reverse recent local tree moves before a broader restore is needed.

Collapsed previews

Collapsed previews can include selected direct members and child-folder summaries without changing actual membership. You can control preview depth, member inclusion, icon/label/status/action visibility, and child folder inclusion.

If every member is excluded from preview, the UI shows an explanatory empty state. Expanding the folder still reveals native rows.

Folder action sheet

The action sheet is context-sensitive. Depending on type, state, lock, hierarchy, and member eligibility, it can offer:

• Edit, focus, pin/unpin, lock/unlock, expand, or collapse.
• Start, stop, pause, resume, restart, or update eligible members.
• Move within the current level, move under a parent, or return to root.
• Clone, export branch, import into branch, scan, repair, or delete.
• Copy folder ID for diagnostics or advanced integrations.

Review destructive confirmations. Deleting a branch can affect nested folders, and runtime actions can affect several workloads at once.

Folder defaults

Docker and VM view settings can save defaults for newly created folders. Save as defaults changes the starting values for future folders and does not rewrite existing folders. Apply to all is a separate explicit bulk operation that intentionally applies supported defaults to existing folders after review. Clear defaults returns future folders to the normal plugin baseline.

Scan and repair hierarchy integrity

Basic Settings provides Tree scan and Tree repair for Docker and VMs.

The scan is read-only and reports:

• A folder referencing itself as parent.
• A parent ID that no longer exists.
• Cyclic parent chains.
• Depth beyond the six-level limit.
• Empty branches as an advisory condition.

Self-links, orphan parents, and cycles are repairable link errors. Depth and empty-branch findings are advisory: automatic repair does not reorganize or delete them for you.

Tree repair refreshes current state, requires a valid expected revision, asks for confirmation, and creates a verified backup. It resets only selected invalid parent links to root, offers undo, reloads the saved tree, and reports remaining link errors and advisory warnings.

Screenshot placeholder — hierarchy scan result

Capture fictional self-parent/orphan findings plus a depth advisory, with repairable and advisory counts visible.

Safe reorganization workflow

1. Create a Recovery snapshot.
2. Switch sorting to manual if order matters.
3. Move one branch at a time.
4. Verify direct members and children on the runtime page.
5. Check Dashboard if that type is displayed there.
6. Use recent-change undo when offered; otherwise restore the safety snapshot.

Common mistakes

• Confusing a hidden preview member with removed membership.
• Expecting manual dragging to persist while an automatic sort mode is active.
• Assigning the same member through overlapping rules without checking priority.
• Deleting a parent without reviewing the nested branch.
• Using folder names as permanent automation identifiers when folder IDs are available.

Next: Folder Editor · Automation, Rules, and Templates