# 4. Search and Navigation
**Purpose.** Nexus Platforms stays usable at scale only if members can find things quickly. This section gives you the fastest search patterns, the taxonomy rules that keep content reusable, and a routing list that answers “Where is X?” in seconds.
#### Quick links (bookmark)
* **Sitemap (full navigation index):**
* **Member Directory (people):**
* **Groups (work rooms):**
* **Q\&A (knowledge hub):**
* **Q\&A Tags:**
* **Q\&A Categories:**
* **Events (calendar):**
* **Journals (curated releases):**
* **Campaigns (time-bound calls):**
* **Knowledge Base (how-to library):**
* **Documentation (reference):**
* **Account (your home/control panel):**
***
### 4.1 Global Search: People, Groups, Posts, Articles, Q\&A, Events
**Operator rule:** when you don’t know where something lives, start with **Sitemap**, then narrow by object type (people / group / Q\&A / event / release).
#### 4.1.1 The fastest “two-pass” search method
**Pass 1 — Find the right container (30 seconds)**\
If you’re unsure which area contains it, open the sitemap and scan by keyword:\
Common anchors:
* People → **Members:**
* Work rooms → **Groups:**
* How-to guidance → **Knowledge Base:**
* Questions / troubleshooting → **Q\&A:**
* Events / webinars → **Events:**
* Curated releases → **Journals:**
* Calls for input → **Campaigns:**
**Pass 2 — Search inside the right container (1–2 minutes)**\
Once you know the lane, use its search/filter tools:
* Directory filters for members
* Group search and group filters
* Q\&A tags and categories
* Event list search
#### 4.1.2 Search patterns that actually work (copy/paste ideas)
**Use two terms:** *domain + object*.
Examples:
* “liquidity stress” (finance)
* “outage continuity” (operations)
* “cyber third-party” (technology)
* “parametric triggers” (risk transfer)
* “verification evidence” (assurance)
* “standards profile” (interoperability)
**People searches (Member Directory)**\
Try:
* Institution type: “central bank”, “ministry”, “regulator”, “insurer”, “exchange”, “utility”
* Role keywords: “CRO”, “CISO”, “CTO”, “resilience”, “continuity”\
Start here:
**Groups searches**\
Search by:
* program name (Quest/Build/Hackathon title)
* domain lane (finance, technology, health, policy, public risk)
* output type (template, checklist, playbook)\
Start here:
**Q\&A searches**\
Search by:
* the “how-to” verb: “submit”, “join”, “host”, “publish”, “tag”
* the object: “event”, “group”, “quest”, “bounty”, “brief”\
Start here:
Then refine with:
* Tags:
* Categories:
**Events searches**\
Search by:
* “orientation”, “office hours”, “clinic”, “webinar”, “hackathon”\
Start here:
#### 4.1.3 When you still can’t find it (the 60-second fallback)
1. Check Sitemap:
2. If it’s likely a question, ask in Q\&A (so the answer becomes reusable):\
3. If it’s a documentation issue, check the KB first:\
***
### 4.2 Tags and Taxonomy (how to tag so content stays usable)
**Principle:** tagging is the platform’s memory. Poor tagging creates noise and duplicates; clean tagging creates reuse.
#### 4.2.1 The minimum taxonomy standard (use everywhere)
When publishing or posting (where tagging is available), use:
* **1 domain tag** (where it belongs)
* **1–3 function tags** (what kind of work it is)
* **0–2 sector tags** (only if relevant)
**Domain examples**
* finance, technology, health, policy, public risk
**Function examples**
* guidance, checklist, template, review-request, research, implementation, standards, verification, incident
**Sector examples**
* banking, insurance, critical infrastructure, public sector, telecom
#### 4.2.2 Tagging rules (to prevent fragmentation)
* Use existing tags whenever possible.
* Check the live vocabulary first:\
* Avoid near-duplicates (e.g., “cyber-risk” vs “cyber risk” vs “cybersecurity”).
* Do not over-tag (more than **5 tags** reduces search quality).
* Tag the **intent** (review-request / how-to / template), not only the topic.
* If you’re unsure, ask before inventing new tags:\
#### 4.2.3 Category vs tag (simple guidance)
* **Category = where it belongs** (the shelf)
* **Tag = what it is about / what it is for** (the label)
Use Categories to keep the structure clean:\
***
### 4.3 Saved Views / Bookmarks (where enabled)
Some areas may provide “save” / “bookmark” / “follow” functions. If your interface shows these options, use them to build a low-noise workspace.
#### 4.3.1 What to bookmark (recommended)
* your 1–3 home groups:
* your key Q\&A tags:
* your next 2 upcoming events:
* one program lane you’re active in:
* Quests:
* Builds:
* Hackathons:
* your KB pages you reference often:
#### 4.3.2 Your “leader dashboard” (manual method that always works)
Even if the platform doesn’t show a saved view button everywhere, you can make a “dashboard” by bookmarking these pages in your browser:
* Groups:
* Q\&A:
* Events:
* Campaigns:
* Journals:
* KB:
* Your account:
***
### 4.4 Common “Where is X?” Answers (quick routing list)
Use this list to route yourself (and others) instantly.
**A) “I want to find a person”**\
Member Directory:
**B) “I want to collaborate with a team / join a work room”**\
Groups:
**C) “I have a ‘how do I…?’ question”**\
Q\&A: \
Ask a question:
**D) “I want to see what’s happening this week”**\
Events:
**E) “I want to publish something reusable”**\
Start by posting in the relevant group (for review), then promote to:
* Journals: \
or capture as how-to guidance in:
* Knowledge Base:
**F) “I want to contribute to structured work with deliverables”**
* Quests:
* Bounties:
* Builds:
* Hackathons:
**G) “I’m looking for official guidance / platform rules / how-to”**
* Knowledge Base:
* Documentation:
* Network Charters:
**H) “I can’t access something”**
* Access gate page: \
Then check membership and ask routing in Q\&A:\
**I) “I don’t know where something is”**
* Sitemap (full index):
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.therisk.global/organization/operations/platforms/4.-search-and-navigation.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.