Skip to content

Bug: UI/UX Feedback: Disruption of graph exploration caused by node detail redirects #2726

@xmp00

Description

@xmp00

Hello team,
The current workflow for inspecting node details in the Community Edition (CE) is significantly disrupting the ability to establish a comprehensive "Full Map" of the environment. Specifically, when clicking a node to view its information with sub levels and connections, the interface transfers the user to a secondary view page that is causing:

  1. Loss of Context: Transitioning to a new page or view causes the loss of the current graph state. When exploring complex attack paths (e.g., from a compromised user to a Domain Controller), maintaining the visual "map" is critical.
  2. Destructive Navigation: The lack of a "Back" button or a way to return to the exact previous layout means that once the view is transferred, the manual work of expanding and arranging nodes must be restarted from scratch.
  3. Limited Sub-node Visibility: Instead of being able to see relationships and sub-nodes in to the depths within the main graph page, the secondary page provides a narrow dataset, making it harder to spot cross-object connections.
Image

When selecting the Administrators node, the tool should allow for in-place expansion of sub-items and connections to build a holistic 'bigger picture.'

Image

The current UI workflow, in this case for 'Administrators' is highly disruptive to graph exploration. Clicking on 'Inbound/Outbound Object Control' or any other option triggers a full-page redirect to a separate view rather than expanding the sub-items and interconnected nodes within the existing graph.

This forced transition destroys the current visual context and also offers no 'back' function to restore the previous layout, making it impossible to maintain a comprehensive map of node relationships.

Image

Suggested Improvement

  1. Side-Panel Implementation: Node details and metadata should ideally be rendered in a collapsible sidebar or an overlay (drawer) on the main graph page. This allows the user to inspect properties without losing the visual layout of the graph.
  2. Keep Layout Static: Clicking a node should not trigger a layout recalculation or a page transfer unless explicitly requested (e.g., a "Deep Dive" button like).
  3. State Persistence: If a view transfer must occur, provide a robust navigation history/back button that restores the previous graph nodes, edges, and positions exactly as they were.

For complex Active Directory environments, the tool's primary value is in the "Full Map" perspective. Forced redirects break the investigative flow and make it difficult to visualize how disparate nodes connect into a single path.

Thank you,
x

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtriageThis issue requires triaging

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions