Tasks

Explore the knowledge graph

The knowledge graph makes the typed relationships between your memories visible. Nodes are memories or entities (Person, Organization, Project); edges are the relationships. This page shows how to explore the graph through the embedded NeoDash dashboard and with Cypher queries.

Audience
Power users who want to inspect their knowledge structure visually — particularly when creating new relationships, when reviewing the client overview, or as preparation for a recall analysis.

Prerequisites

  • Signed-in knowmind account
  • At least some memories with relationships in the Memory Store
  • Business plan or higher for advanced Cypher queries in the dashboard
  • Basic Cypher (Neo4j query language) for custom queries

Steps

  1. 1

    Open the NeoDash dashboard

    From the cockpit under Knowledge Graph, or directly:

    text
    https://knowmind.de/dashboard/graph

    The dashboard runs as an iframe-embedded NeoDash and connects on first launch to the knowmind Neo4j instance. The first session asks for database credentials.

    Outcome: The NeoDash UI appears with three pre-built cards: client overview, persons per organization, recent relationships.

  2. 2

    Set up the connection

    When NeoDash asks for credentials on first launch:

    text
    Protocol:  neo4j+s
    Hostname:  knowmind.de
    Port:      7687
    Database:  neo4j
    Username:  neo4j
    Password:  (in the cockpit under Profile → Knowledge Graph access)
    Note

    Password reveal in the cockpit currently on request

    The UI to reveal the read-only password under "Profile → Knowledge Graph access" is in the backlog. Until it ships, Business and Enterprise customers receive the password on request through info@schuebeler-consulting.de.

    Outcome: NeoDash establishes a Bolt connection over TLS. A status indicator at the bottom-left says "Connected".

  3. 3

    Example: list all persons in the workspace

    Create a new NeoDash card, type Table, with the following Cypher query:

    cypher
    MATCH (p:Person)
    WHERE p.tenant_id = $tenantId
    RETURN p.name AS name, p.role AS role, p.email AS email
    ORDER BY name
    LIMIT 50;

    The dashboard fills $tenantId automatically from your session — you do not set it manually.

    Outcome: A table of every Person node in your workspace.

  4. 4

    Example: visualize an organization's connections

    Card type Graph:

    cypher
    MATCH path = (org:Organization { name: $orgName, tenant_id: $tenantId })
                  -[r*1..2]-(n)
    WHERE n.tenant_id = $tenantId
    RETURN path
    LIMIT 100;

    With r*1..2 the query follows relationships up to two hops. Use the dashboard's parameter field to set $orgName to your client organization's name.

    Outcome: An interactive graph visualization, nodes as circles, edges labeled with the relationship type. Click a node to inspect its properties.

  5. 5

    Example: cluster across multiple hops

    For a cluster analysis — which persons, projects and documents are connected within three hops:

    cypher
    MATCH path = (start:Person { name: $personName, tenant_id: $tenantId })
                  -[*1..3]-(n)
    WHERE n.tenant_id = $tenantId
    WITH n, count(path) AS paths
    RETURN labels(n)[0] AS type, n.name AS name, paths
    ORDER BY paths DESC
    LIMIT 25;

    Outcome: A ranking of nodes connected within three hops, sorted by path count. Surfaces a person's closer surroundings.

  6. 6

    Save and share cards

    NeoDash stores dashboards inside Neo4j itself. To save, click Save in the top-right and enter a dashboard name (e.g. Client overview). Other power users in your workspace will see the dashboard after a reload.

    Outcome: The dashboard appears under Saved Dashboards and is available to every member of your workspace — no separate permissions to set.

Verify the result

  • NeoDash's status indicator says "Connected" against knowmind.de:7687.
  • A sample query MATCH (n) RETURN count(n) returns the expected node count for your workspace.
  • A CREATE (:Test) attempt is rejected with an error (read-only user). This is the desired behavior.

Troubleshooting

Error messageCauseResolution
NeoDash iframe does not loadA browser extension blocks WebSocket connections to :7687, or a corporate proxy does not allow the Bolt protocol.Test in the browser's incognito mode. If that works, an extension is blocking. On a corporate network ask IT to allow outbound WebSocket connections to knowmind.de:7687.
Cypher query reports Neo.ClientError.Security.ForbiddenA write-side Cypher statement (CREATE, MERGE, DELETE, SET) was attempted — the read-only user does not allow it.Perform write operations through MCP tools, the REST API or the relationship editor. See the 'Manage relationships' task.
Query returns an empty result although data existsThe query is missing the tenant_id filter. Without it the read-only user still sees nothing (database-level RLS) but the query fails silently.Add WHERE n.tenant_id = $tenantId to every query. The dashboard fills $tenantId automatically.

Related