---
question: How do I change or add a SPARQL search topic?
kind: task
via_web: available
via_cli: na
via_python: na
via_api: na
via_config: na
ref_web: Settings › Search
prereq: You are an owner or admin of this workspace.
next:
  - /capabilities/platform/configure-workspace-search
  - /capabilities/platform/run-a-search
  - /capabilities/build/knowledge-graph/graph-overview
---

# Edit a search topic

A **topic** is a search layer defined by SPARQL templates: which class is searched, how results and detail pages render, and optional sections (experiences, related people, and similar). Built-in topics such as **person** and **organization** ship in the product. Owners and admins can override them or add custom topics from **Settings › Search**.

## Web UI

### Open the topic editor

From **Settings › Search**, select a topic or choose to add one. The editor lists each query role (results, header, sections, image, row) with the SPARQL Nexus runs against graphs this workspace may read.

![Workspace Settings on Search: the People topic editor](/abi/Screenshot_Search_Topic.png)

*The editor for the built-in People topic: labels, description, ontology class, icon, order and the graphs it reads.*

### Test a query

Use **Test** on a query block to run it against the workspace graphs with sample placeholders. Fix validation errors before saving. Only `SELECT` queries with the required variables for each role are accepted.

### Save or reset

Save writes the topic for this workspace. **Reset** on a built-in topic removes the override and restores the shipped definition.

### See it in Search

Open Search, enable the topic in [Configure workspace search](/capabilities/platform/configure-workspace-search) if needed, then pick the topic in the scope column. Topic views use **Results**, **Ontology**, and a detail tab (for example **Profile**). Result and detail blocks can show the SPARQL that produced them.

Modules can register topics in code (for example a Products topic on a key-account workspace). Those appear in the topic list like built-ins until you override them here.

## CLI

Not applicable.

## Python

Not applicable. Topic definitions in a module are Python or pipeline seed data, not something you edit from a project script at runtime.

## REST API

Not applicable. Nexus exposes search topic routes under `/api/search/topics` for the web UI; they are not listed in the generated [API reference](/api) this docs site ships today.

## Config

Not applicable.