​
Overview

Most screens in Simnet are a list of resources with the same toolbar. Learn it once and every screen behaves the same way — with a few screen-specific extras noted below. Every list has one. What it matches varies by screen, and it’s worth knowing which are narrow:
Two searches only cover what the browser already fetched, not your whole history:Events searches within a 500-record window. Audit Log searches within the current 25-row page.On both, narrow the date range instead of relying on search. Every other list searches server-side.

​
Filters

A Filters dropdown, showing a dot when active, with a Reset Filter entry once you’ve changed it. Options are screen-specific — the Virtual Machines status list, the Volumes type and state pair, and so on. Two behaviours are worth knowing generally:
Filter lists are often shorter than the real set of states. Volumes has eleven states and offers six; VM Snapshots omits Expunging. A resource in an unlisted state appears only under the “All” option, never under a specific filter.
The ISOs status filter is broken — selecting Ready or Not Ready returns nothing at all. Leave it on All ISOs. Reported as a defect.

​
Sorting

Click a column header. Sorting is three-state: ascending → descending → cleared, so a third click returns to the natural order rather than sticking.
Not every header sorts. On ISOs, the Display Text, Size and Created headers look clickable but do nothing — they’re bound to columns that were never defined. Another known defect.

​
The Resources dropdown on Virtual Machines

Virtual Machines has an extra sort control labelled Resources, offering five keys the columns don’t expose: Each cycles ascending → descending → cleared, same as a column header.
VCPU and Memory are the two that aren’t available anywhere else, and they’re the ones you want when hunting for an oversized machine to downsize.

​
Tag grouping — Virtual Machines

Tags on the Virtual Machines screen do more than label. Click a tag chip on any row and you get four actions: Each group header shows the tag name, a count like (2 VMs), and a Clear Group button. Machines not in any group follow underneath, and the sort you’ve applied is preserved inside each group.
Clear Group clears one tag at a time. With several groups active you clear them individually — there’s no “clear all grouping” control.
When a tag filter or exclusion is active, a Filters Active banner appears above the table reporting {n} included and {n} excluded, with Clear Filters.
Grouping is the practical way to run a fleet from one screen: tag machines prod, staging and ci, then group by prod to see production together without losing sight of the rest. It beats filtering when you want context rather than isolation.

​
Adding and removing tags

The dialog has one field, Tag Value, with placeholder “e.g., Production, Development, Web Server”.
Tags are a single value, not a key–value pair — whatever you type becomes both. And there’s no edit: correcting a typo means deleting the tag and adding it again.Validation is minimal: only empty values and exact duplicates on the same machine are rejected. There’s no length or character checking, so Prod, prod and prod are three different tags that will group separately. Agree a convention with your team before tagging a fleet.

​
Bulk selection

Checkboxes select rows; a banner appears above the first selected row. On Virtual Machines it offers Start, Stop, Restart and Delete for the selection, plus Clear Selection.
Bulk operations fire in parallel, not as a queue. Fifty selected machines means fifty simultaneous requests, and some may fail on quota or capacity while others succeed. Check Jobs for the real per-machine outcome rather than assuming the batch worked.
Several screens show checkboxes that do nothing — Templates, ISOs and the storage lists have row selection wired up but no bulk actions behind it. If selecting rows produces no banner, that screen has none.

​
Cards or table

Virtual Machines and Kubernetes offer a Cards / Table toggle. Everything else is table-only.

​
Why a column disappeared

Columns drop out as the window narrows, silently, with no indicator. On Virtual Machines the two IP columns collapse into one below roughly 656px, Resources goes below ~848px, Zone below ~1000px (it also needs a viewport wider than 1280px), and Tags below ~1060px.Public IPs hides Allocated and Zone below about 1400px.If a column you expect is missing, widen the window before concluding the data is absent. There is no column-visibility control on Virtual Machines — display is width-derived only.
Kubernetes does have a show/hide-columns menu, but it lists internal identifiers rather than the labels in the header — a rough edge of that preview.

​
Expanding a row

Most lists have a chevron that expands a row in place, showing fields the columns don’t have room for — identifiers, accounts, creation times. On Shared Filesystems the expanded row includes the NFS Mount Command with a copy button, which is the fastest way to mount one.
Try expanding before opening a detail page. It’s usually enough to answer “what is this thing” without losing your place in the list.

Navigating the console

The sidebar, Create menu, search, and taskbar.

Virtual Machines

Where tag grouping and the Resources sort live.

Jobs

Confirming what a bulk action actually did.