Skip to content

Layouts

Layouts save your panel arrangements and configurations, allowing you to quickly recreate specific views and share them with your team. They're stored in the cloud and synced across sessions.

What Layouts Save

A layout captures:

  • All panels in layout tabs (Plot, Table, Log, Value, and Action)
  • Panel positions and sizes in the grid
  • Panel settings - Fill area, line styles, display options
  • Signal selections, scopes, and colors - Which signals are shown, whether they are portable or trace/agent-scoped, and their visualization colors
  • Panel titles - Custom names for each panel
  • Panel descriptions - Optional descriptions for documenting panel purpose

Layouts do NOT include:

  • The actual data (only configuration)
  • Connection settings
  • Time range selections
  • Runtime-only segment instance IDs from the current session
  • Extension tabs
  • Settings tabs

Manual Saving Only

Layouts are never auto-saved. All changes require an explicit Save or Save as new.

Multi-Trace Support

Layouts can work with multiple traces simultaneously. When configuring signals in panels, you can choose between:

  • Portable signals - Work with any trace and/or agent that contains matching signal paths
  • Scoped signals - Tied to a specific trace and/or agent

Portable configurations are useful when sharing layouts with team members who may load different trace files with similar signal structures.

Saved layouts rebind to current data

Layouts save logical signal bindings and colors, not transient segment-instance IDs. When you load a layout, Zelos resolves each saved signal against the currently open traces and/or agents using the saved path and scope. If a panel temporarily expands one logical signal into multiple segment-bound series or cells so you can inspect overlapping data, that expansion is recomputed from the current data when the layout loads rather than stored directly in the layout.

Managing Layouts

Layouts live in the Data view of the right sidebar (toggle with Cmd+J / Ctrl+J). Its Layouts section lists your personal layouts and your team's shared ones.

Layouts are stored per organization. Signed in without one, the section reads No organization yet and there is nothing to save into. Set up an organization from Home or Settings first.

Creating a Layout

  1. Arrange panels in your workspace exactly as desired
  2. Open the right sidebar (Cmd+J / Ctrl+J)
  3. Click Save as new in the Layouts section
  4. Enter a layout name (max 100 characters)
  5. Toggle Personal/Shared:
  6. Personal (👤) - Only visible to you
  7. Shared (👥) - Visible to your entire team
  8. Click Save

Save Layout

Saving a layout.

Loading a Layout

Click any layout name in the right sidebar to load it. The layout replaces your current panel arrangement.

The list has two sections: Pinned on top, then Recent. Pin a layout from its menu to keep it in the first section.

Panel compatibility on restore

  • Action panels stay in the layout, but they only execute in live workspaces. If you load the same layout while browsing trace files, the panel shows a live-only state until you reconnect to an agent.
  • Legacy Gauge panels from older saved layouts are still preserved in layout data, but current app builds render them as an unsupported placeholder rather than an interactive gauge.

Editing a Loaded Layout

Once a layout is loaded, you can keep refining it before saving again.

Rearranging Panels

  • Move a panel within the current tab by dragging its header
  • Resize a panel by dragging its edges or corners
  • Move a panel to another tab by dragging its header onto that tab

During drag-and-drop, Zelos shows a preview of whether the drop will merge into an existing panel or insert a new row. When you drag near layout edges or across tabs, the layout auto-scrolls so you can reach off-screen targets without dropping first.

Adding Signals to an Existing Layout

Signal drag-and-drop uses two different intents:

Drop location Result
Center of a Plot, Table, Log, or Value panel Add the signal to that panel
Center of an Action panel Signal drops are rejected
Top or bottom band of a panel Insert a new Plot panel row at that boundary
Gap between rows or empty layout space Insert a new Plot panel row at the nearest row boundary

New rows default to Plot

When you create a panel directly from a signal, Zelos creates a new Plot panel. To start with a Table, Log, or Value panel, first create that panel from Add Panel, then drop data into it.

Reusable Layouts

Signals dragged from the tree into panels are saved as portable bindings by default. This keeps shared layouts useful across similar traces and live agents. Use Edit Panel -> Data when you intentionally want to scope a signal to a specific trace or agent.

Double-Click Behavior

Double-clicking a signal in the sidebar creates a new Plot panel at the bottom of the active layout tab.

Updating a Layout

When you have a layout loaded and make changes:

  1. Notice the modified indicator (amber dot) next to the layout name
  2. Click Save to update the existing layout with your changes
  3. The Save button is only enabled when unsaved changes exist

Alternative: Use Save as new to create a new layout instead of overwriting.

A layout from another organization

If you switch organizations while a layout is loaded, Save is disabled and its tooltip reads This layout belongs to another organization. Save as new still works, so you can keep the arrangement as a layout in the organization you are in now.

Layout Actions

Click the menu next to any layout for additional actions:

Pin

  • Move the layout into the Pinned section at the top of the list
  • Choose it again to unpin

Rename

  • Edit the layout name inline
  • Press Enter to save, Esc to cancel
  • Click outside to cancel

Share with Team

  • Convert a personal layout to shared
  • Makes it visible to your entire team
  • Only available for personal layouts

Details

  • Open the layout's own page in the sidebar (see Layout Details)
  • Shows who can see it, when it changed, its version history, and its tags

Delete

  • Permanently remove the layout and its version history
  • Cannot be undone

Layout Details

Choose ⋮ → Details on any layout to replace the Data view with that layout's own page. The header names the layout; its Back to Data icon or Esc returns to the lists.

Details says who can see the layout — your team, or only you — when it was last updated and by whom, and when it was created. The original author is named when someone else made the last change.

Times use the same format throughout the page: Today, 3:42 PM, Yesterday, 6:03 PM, or a date and time such as Jun 28, 1:30 PM.

The header's carries the same actions as the layout's own row — Pin, Rename, Share with Team while the layout is still personal, and Delete. Details is the one thing left out, since you are already on it. Rename edits the title in the header.

Version History

Every save records a version, Google Docs style: creating a layout is version 1, and each content-changing save (panels, name) appends the next version. Saves that change nothing, and personal/shared toggles, don't create versions. The last 100 versions are retained per layout — plus any named versions, which are kept forever.

The History group lists them newest first. Each entry shows:

  • The save time — or the version's name, if you gave it one, with the save time moving to the line below
  • Its revision number, and current on the latest
  • Who saved it
  • A "restored from …" marker when the version was created by a restore

Choose an entry to expand it and see what changed against the previous version: panels added, removed or changed, tabs added or removed, and renames. The oldest entry has no previous version to compare against, and says so.

Naming a version

Open an entry's and choose Name this version to give it a name (like "Golden bench config"). Named versions show their name in place of the save time — and they are kept forever: the version retention limit never prunes them. Rename version on a named entry changes it; clearing the name makes the version ordinary again.

Restoring a version

Open an older entry's and choose Restore this version. Restoring is always safe: the selected version's content is applied as a new version on top of the history, so the state you're leaving stays restorable — nothing is ever rewritten or lost. If the restored layout is currently loaded, your workspace updates immediately.

Layouts saved before version history

Layouts created before this feature start with no history. Their first save from now on records the pre-save state as version 1, so the state being replaced is always restorable.

Tags

Tags is edited in place, the same picker traces and notebooks use: + attaches a tag or creates one, the on a chip detaches it, and changes save as you make them.

Visual Indicators

Active Layout

  • Colored left border on the active layout
  • Shows which layout is currently loaded

Modified Indicator

  • Amber dot appears when unsaved changes exist
  • Only shows for the active layout
  • Disappears after saving

Personal vs Shared

  • 👤 icon = Personal layout
  • 👥 icon = Shared layout
  • Shown next to layout name

Hover Information

Hover over any layout to see:

  • Layout name
  • Creator email
  • Creation date
  • Layout ID
  • Shared status
  • Unsaved changes status (if applicable)

Search and Filter

The right sidebar search filters layouts by:

  • Layout name
  • Creator email
  • Layout ID

Type in the search box at the top of the right sidebar to filter all layouts.

Keyboard Shortcuts

Action Shortcut
Toggle right sidebar Cmd+J / Ctrl+J
Confirm rename Enter
Cancel rename Esc
Search right sidebar Cmd+Shift+F / Ctrl+Shift+F

Best Practices

Personal Layouts

Use for personal workflows, experiments, and work-in-progress configurations.

Shared Layouts

Create shared layouts for:

  • Standard debugging scenarios
  • Common test configurations
  • Team onboarding views
  • Customer demonstration setups

Panel Descriptions

Add descriptions to panels to document their purpose. This is especially helpful when sharing layouts with team members who may not be familiar with the specific signals or configuration choices.

Naming Conventions

Use descriptive names that indicate:

  • What the layout shows (e.g., "Motor Diagnostics")
  • When to use it (e.g., "Startup Sequence")
  • Who it's for (e.g., "QA Test Suite")

Next Steps

  • Panel Types

    Understand different panel options

  • Sidebars

    Learn about the right sidebar and layout management

  • Workspace

    Master workspace features and tabs