# Dashboard and management (/docs/dashboard)

> Use lists, detail pages, views, websites, services, IP management, and the audit log.

## Common navigation [#common-navigation]

Select an item in a list to open its detail page. View and edit it there. Delete or revoke actions appear at the end of the detail page and require confirmation. Lists do not place edit and delete actions next to each other.

Servers, websites, backup plans, projects, templates, status pages, and notifications offer table and card views. The browser stores the selection per list. Servers default to cards; the other lists default to tables. Services, IP management, maintenance, rules, and API keys use tables.

## Websites [#websites]

Open a monitor from the list and use the **Settings** tab on its detail page to edit it. The list loads check history for the visible page in one request instead of one request per row. History records observations; it does not prove that a full security assessment was performed.

Websites can also be targets of backup plans and jobs without a server assignment. See [Backup plans](/docs/backups).

Successful backups appear green; warnings appear amber. Relative times in the backup list, backup detail, and server maintenance tab follow the selected language.

## Services and IP management [#services-and-ip-management]

Services remain grouped by server; IP assignments remain grouped by network. These lists load all available data pages, then show 25 rows per display page. Use **Next** and **Previous** to navigate. A network without assignments remains visible as one row. A group can span multiple pages.

## Maintenance navigation [#maintenance-navigation]

When you open a maintenance window from a server's maintenance tab, the back link returns to that server and tab. Deletion returns there too. Windows opened from the maintenance list link back to that list.

## Audit log [#audit-log]

Under **Settings → Audit log**, each page contains 25 events. Search matches action, entity, user email, and IP address without case sensitivity. Use pagination to reach older events. Entity links open the relevant detail page if the object still exists and you have access.

## Administration [#administration]

Pages under `/admin` require the platform admin role. An organization admin role is not sufficient. Organization plan changes use active plans from the API, including custom plans. The relevant access requirements still apply.

## Sort tables [#sort-tables]

Click a column heading with an arrow to sort the table. Click again to reverse the direction. You can also use Tab and Enter or Space. Numbers sort numerically and dates sort by their actual timestamp. Missing values remain last in both directions.

Sorting is available in dashboard and administration lists, including alerts, rules, API keys, delivery logs, website checks, and server process and package lists. Paginated lists sort before splitting rows into pages. Services stay grouped by server and IP assignments by network; sorting applies within each group. The server process list and the latest 100 website checks sort their displayed data window.

You can combine search and sorting. Changing the sort resets pagination. The selection lasts while the view is open. Action columns and history graphs do not have sort buttons.

The audit log sorts all matching events on the server by time, action, entity type, user email or IP address. Search and organization permissions still apply. Backup history supports sorting by status, start and completion; see [Backups](/docs/backups).

After a sort click, the server list keeps its row order while live metrics continue to update. Click again to sort using current values. New or previously filtered-out servers appear last until the next sort click. Missing and stale metrics are shown as “—” and sort last.

Totals and averages include only available, current metrics. If a metric has no available values, the summary row also shows “—”.