Skip to main content
The list view shows every item of a type in a sortable, filterable grid. The context graph visualizes the relationships between items and lets you traverse them. Most day-to-day work happens in the list view. The context graph comes out when you need to understand impact, ownership, or dependencies.

​
The list view

List view for a MacBooks item type showing source, name, and key columns with search and filter controls

The list view for an item type

Open any item type in the Databases tab to see its list view. By default, the columns are the key field, the name field, and a handful of others Serval picks based on the type. In the list view, you can:
  • Click Columns to pick which fields show
  • Filter on any column
  • Click on a column to sort ascending or descending
  • Search in the search box
  • Move between pages (500 items per page by default)
  • Save and share views
  • Set a default view
Open an item’s Related tab to browse its connections:
  • Reference fields: items and users referenced by this item’s fields, and items whose reference fields point to this item.
  • Relationships: connections stored in relationship types, in either direction.
Click a connected item’s name to open it, or a user’s name to open their profile. To add a relationship, click Create relationship. Select a Relationship type and a Related item. If this item can be either endpoint, choose the Direction, then click Create relationship to save. With permission to edit the relationship, click the remove (×) button beside the connected item. This leaves the connected items in place. To change a reference-field connection, edit the field on the item that stores it.

​
The context graph

Click any item on its detail view to see its context graph.
Context graph for a virtual network item showing connected nodes and directional edges alongside the item's field detail

The context graph for an item

The context graph visualizes the item reference fields you set up in Schema design as a navigable network. Every item is a node. Every reference field, and every relationship type, is a directional edge.

​
A person’s items

A user’s profile has an Items tab that works like a database dashboard scoped to that person. The Tables pane on the left lists every table whose items reference the user through a user reference field, grouped by database, with the field name and the number of items under each table.
  • Graph: the first row opens the user’s context graph across every table. A table with more than a handful of references collapses into a footer such as 54 Accounts; click it to browse those items. The legend starts with items only, and you can switch on groups, teams, tickets, and other neighbors.
  • A table: pick a table to see its items in the familiar table view, pinned to the user with a read-only filter chip such as Account Manager is Aashna Panchal. Add filters, search, and show archived items as usual. Open in [database] takes you to the table in its database with the same filter applied.
When you view someone else’s profile, the tab only shows items in teams you belong to.

​
What the Help Desk Agent sees

The Help Desk Agent traverses the same graph when it resolves tickets. If a user opens a ticket about “my laptop,” the agent walks from the user’s item to their assigned computer, then to that computer’s recent incidents, hardware specs, and assigned software. Configure which item types the agent can see in Administration.

​
Workflows on the graph

Workflows can traverse the same relationships from code. The typical pattern: a server goes down, a workflow reads the graph to find every service that depends on it, then fans out remediation or notifications to the owners of each.