Skip to main content
Atlas logoAtlas
  • About
  • Pricing
  • Docs
Log inStart your workspace
Help Center
  • Maps overview
  • Generate a knowledge map
  • Edit, export, and manage a knowledge map
  • Knowledge map controls and node types
  • Read and use a semantic map
  • Troubleshoot maps

Knowledge map controls and node types

Knowledge map controls help you move between overview and detail, inspect relationships, adjust generated structure, and reuse the visible map outside Atlas.

What this page covers

Learn the controls, node types, edges, selection behavior, navigation, and map states.

Core interactions

ControlWhat it doesUse it when
ZoomChanges the visible scale of the map.You need either a high-level overview or readable node detail.
PanMoves around the canvas.The map is larger than the current viewport.
Select nodeOpens or highlights a concept.You want to inspect a claim, idea, method, or finding.
Select edgeShows the relationship between nodes.You need to understand why two concepts are connected.
Open nested nodeMoves into a more detailed map level.A concept needs decomposition.
Reset viewReturns to a stable framing.You are lost in the canvas.
ExportCaptures the map for sharing or reuse.You need the map outside Atlas.

Generated structure

Knowledge maps are generated from source material. Node labels and relationships summarize the source, so treat the map as an interpretation layer. Verify important nodes against the original document before relying on them.

Editing

Use editing to clarify labels, remove noise, or make the map easier to present. Do not edit a map in a way that makes it look more certain than the source. If you change meaning, capture that as your own interpretation in notes rather than as source-derived structure.

Nested maps

Nested maps are useful when one concept contains multiple subclaims, mechanisms, steps, or evidence clusters. Use nesting to keep the top-level map readable while preserving detail.

Export quality

Before exporting, zoom to a level where labels are readable and important relationships are visible. A good export should communicate the structure without requiring the viewer to already know the source.

Common mistakes

  • Treating a map as proof instead of a navigation aid.
  • Exporting while zoomed too far out.
  • Editing away caveats that matter in the source.
  • Trying to force every source into a dense map when a summary or note would be clearer.

Understand node types

Map nodes represent concepts, claims, methods, evidence, and structures that Atlas identifies in source material. Edges describe how those nodes relate.

Common node types

Node typeRepresentsExample
ConceptAn important idea, term, entity, or theme."retrieval-augmented generation"
ClaimAn assertion made or implied by the source."visual maps improve recall"
EvidenceSupport for a claim.experiment result, quote, statistic
MethodA process, technique, or study design.survey, benchmark, intervention
FindingA reported result or conclusion."Group A outperformed Group B"
LimitationA caveat, boundary, or weakness.small sample size, missing controls
QuestionAn unresolved issue or research direction."Does this generalize to novices?"
SectionA structural part of a document.introduction, methods, discussion

The exact labels can vary by source and generation model. Use each type to interpret the map while allowing for labels that fit the current source better.

Edge types

Edges describe relationships such as:

  • supports
  • contradicts
  • causes
  • depends on
  • contains
  • compares with
  • leads to
  • is evidence for.

Read edge labels carefully. A weak or vague edge is a sign to inspect the source passage or regenerate a narrower map.

Nested nodes

A nested node contains a more detailed structure beneath a high-level concept. Use nested nodes when the top-level map is too dense or when a concept contains multiple subclaims.

Verification

Map nodes are summaries. Before quoting, citing, or publishing a claim from the map, open the source and confirm the underlying evidence.

Reading strategy

  1. Start with high-degree nodes, which often represent central ideas.
  2. Follow edges to understand relationships.
  3. Open nested nodes only when the top level is clear.
  4. Check limitations and contradictions before drawing conclusions.

Related documentation

  • Read and use a semantic map
  • Troubleshoot maps
  • Maps overview

On this page

Atlas logo
Atlas

The visual and verifiable workspace
for understanding research.

Product

  • About
  • Features
  • Pricing
  • Docs

Resources

  • Blog
  • Researchers
  • Students
  • Analysts

Company

  • Support
  • Terms of Service
  • Privacy Policy

© 2026 AgentScale AI Pte. Ltd. All rights reserved.