1Open the list
Navigate to /systems
From any page click Administration → Connected Systems (sometimes labelled System Editor). The URL becomes /systems. The list is the entry point for everything in the System Editor.
The plugin contributes two routes: /systems (this list, always visible in nav) and /system-editor/<name> (the per-system editor, hidden from nav and reached via Edit). Operators rarely need to type the editor URL directly.
What you see on first load
A page header with the title "Connected Systems", the four stats cards across the top, a filter row, the systems grid, and pagination at the bottom. The aria-label "System definitions list" identifies this view in screen readers and tour scripts.
2Read the stats cards
The four stats cards at the top give you an at-a-glance health snapshot of your integration estate.
| Card | What it counts |
|---|---|
| Systems | Every registered system regardless of state. |
| Commands | Total commands across all systems. A system without commands isn't useful — flag those for follow-up. |
| Object Types | Distinct object-type entries across all systems (User, Group, Ticket, etc.). High counts indicate broad coverage. |
| Connection issues | Systems where the last Test Connection attempt failed or hasn't been run recently. Click into one to investigate. |
3Switch view modes
Four icon buttons on the toolbar swap the layout. Each has a stable test id you can target from a tour script.
| Button | data-testid | Best for |
|---|---|---|
| ⊞ Grid | view-mode-grid | Default. Card-per-system, three columns wide. |
| ☰ Table | view-mode-table | Many systems, side-by-side columns: Name, Type, Commands, Last Test, Actions. |
| 🌳 Tree | view-mode-tree | Group by system type (e.g. all SCIM systems together). |
| 🕸 Mind map | view-mode-mindmap | Spatial overview that clusters systems sharing tags / object types. Each node opens a detail card. |
The mind-map (aria-label "System Architecture Mind Map") has its own zoom, layout, fullscreen, and right-click context menu. Right-click a node for "Edit System", "Isolate" (hide everything else), and "Reset" (restore the full graph).
4Search systems
Find by name
Type into the Search input above the list. Filtering is live and matches across system name and description. The input has the test id systems-search-input and aria-label "Search systems".
5Filter by system type
Pick a type
Use the Type dropdown next to the search box. It lists every distinct system type registered in your tenant — common values include scim, oauth-rest, graphql, jdbc, nowconnect, and any custom type templates. The control has the test id systems-type-filter and aria-label "Filter by system type".
Clear filters
The Clear filters button (test id systems-clear-filters) appears once you've applied any combination of search + type. One click resets both fields to the default.
6Paginate
Per-page and page controls
The pagination strip at the bottom of the list (test id systems-pagination, aria-label "System definitions pagination") shows Page X of Y, per-page count, and Prev / Next buttons.
Default page size is 24 systems. Increase it for large estates so you can scroll the whole list at once.
7Open a system
Click a card or row
Click any system card (or row in table view) to open it in the editor. The browser navigates to /system-editor/<name> and the 10-tab editor shell loads with the System Details tab active.
🔵 EntraID
🟦 ServiceNow
🟪 Workday
Edit (alternative)
Each card has an explicit ✏️ Edit button (aria-label "Edit system <name>"). Click it for the same effect as opening the card. In table view there's an Edit action in each row.
You can browse and Test without write rights, but Save is gated by system-editor:system · edit. The Save buttons inside the editor are visually present but disabled when your role is read-only.
8Create a new system
Click + Create New System
The button on the top-right of the toolbar has the stable test id create-system-button and aria-label "Create new system definition". Click it to open the editor at /system-editor/new.
If your tenant has no systems yet, an empty state shows the same button in the centre of the page (this version is wrapped in a Protected component and hides when your role lacks system-editor:system · create).
Where to go from here
The editor opens with the System Details tab active. From there you typically:
- Pick a system type (or import an OpenAPI spec to bootstrap one).
- Configure Connection and Authentication.
- Define Commands in the Designer.
- Optionally expose commands as MCP tools for AI agents.
- Save.
Each step is covered in the next four guides. Start with System Details & YAML Editor.