> For the complete documentation index, see [llms.txt](https://docs.mulearn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mulearn.org/how-to-use-the-platform/general-pages/search.md).

# Search

#### Purpose

The **Search** module helps mentors discover learners, mentors, and campuses across the μLearn community. You can search for members, explore their profiles, and view campus information and statistics.

#### Page Overview

The Search page is divided into three sections:

* **Learners** – Search and browse learner profiles.
* **Mentors** – Search and browse mentor profiles.
* **Campuses** – Search campuses and view campus details.

Each section provides search functionality tailored to the selected category.

#### Features/Sections

**Learners**

* Search learners by **name**, **skill**, or **role**.
* Learner cards display:
  * Profile photo
  * Name
  * Skills and interest tags
  * MuID
  * Karma points
* Selecting the arrow on a learner card opens the learner's profile.

**Mentors**

* Search mentors by **name**, **skill**, or **role**.
* Mentor cards display:
  * Profile photo
  * Name
  * Skills and expertise
  * MuID
  * Karma points
* Selecting the arrow on a mentor card opens the mentor's profile.

**Campuses**

* Search campuses by **name**, **code**, or **role**.
* Filter campuses by:
  * Name
  * Code
  * Zone
  * School
  * College
* Campus cards display:
  * Campus name
  * Zone
  * Member count
  * Campus code
* Selecting **View Campus** opens the campus details page.

#### Campus Details

The Campus Details page provides information about the selected campus, including:

* Campus name
* Zone
* Campus level
* Campus code
* Total Karma
* Campus Rank
* Total Members
* Active Members
* Weekly Karma Trend chart

#### Available Actions

* Search learners.
* Search mentors.
* Search campuses.
* Filter campus search results.
* Open learner profiles.
* Open mentor profiles.
* View campus information and statistics.

#### Step-by-Step Workflow

1. Open **Search** from the sidebar.
2. Select **Learners**, **Mentors**, or **Campuses**.
3. Enter keywords in the search bar.
4. Browse the filtered results.
5. Select the arrow on a learner or mentor card to open their profile.
6. Select **View Campus** to open the campus details page.

#### Notes

* The search results update based on the selected tab.
* Campus filtering is available only in the **Campuses** section.
* Learner and mentor cards provide direct access to individual profiles.
* Campus cards provide access to detailed campus statistics and performance information.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mulearn.org/how-to-use-the-platform/general-pages/search.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.