> 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/learning-circle.md).

# Learning Circle

#### Purpose

The **Learning Circle** page allows mentors to discover and join collaborative learning groups based on shared interests or topics. Learning Circles provide a space where members can learn together, collaborate, and participate in discussions led by a Circle Lead.

#### Page Overview

The Learning Circle page displays all available Learning Circles. You can search for circles, filter the displayed results, browse through multiple pages of results, and view detailed information before requesting to join a Learning Circle.

#### Features/Sections

* **Search Bar** – Search Learning Circles by name, topic, or organization.
* **Circle Filter** – Filter the displayed circles using:
  * **All Circles**
  * **My Circles**
* **Learning Circle Cards** – Each card displays:
  * Interest Group
  * Learning Circle name
  * Organization or college
  * Number of members
  * Member status
  * Join button
* **Pagination** – Navigate between pages when multiple Learning Circles are available.
* **Learning Circle Details** – View detailed information about a selected Learning Circle before requesting to join.

#### Available Actions

* Search for Learning Circles.
* Filter the displayed Learning Circles.
* Browse Learning Circles using pagination.
* View Learning Circle details.
* Send a request to join a Learning Circle.

#### Step-by-Step Workflow

1. Open **Learning Circle** from the sidebar.
2. Use the search bar to find a Learning Circle by name, topic, or organization.
3. Select **All Circles** or **My Circles** to filter the displayed results.
4. Browse the available Learning Circles.
5. Select a Learning Circle to open its details page.
6. Review the Learning Circle information.
7. Select **Join Circle** to send a join request.
8. Wait for approval from the Circle Lead before becoming a member.

#### Learning Circle Details

The Learning Circle details page includes:

* Learning Circle name
* Current status
* Organization or college
* Description
* Circle Lead
* Metrics, including Rank and Karma
* Interest Group
* Members
* Meetings

#### Join Request Status

After selecting **Join Circle**, one of the following notifications may appear:

| Status                        | Description                                                            |
| ----------------------------- | ---------------------------------------------------------------------- |
| **Join request sent**         | Your request has been successfully submitted to the Circle Lead.       |
| **Join request already sent** | Your previous request is still awaiting approval from the Circle Lead. |

#### Notes

* Mentors can discover and join Learning Circles but cannot create new Learning Circles.
* The **My Circles** filter displays only the Learning Circles you have joined.
* Joining a Learning Circle requires approval from the Circle Lead.
* If no members have joined, the Members section displays **No members yet**.
* If no meetings have been scheduled, the Meetings section displays **No meetings yet**.


---

# 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/learning-circle.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.