> 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/roles-and-responsibilities/enabler.md).

# Enabler

Enablers are the **operational backbone** of μLearn at the community level within partner institutions. They are faculty members who have taken on structured responsibility within μLearn bridging the gap between the formal academic environment they operate in and the proof-of-work ecosystem their students are building in.

### <mark style="color:$primary;">Who Enablers Are</mark>

Enablers are faculty members from colleges and institutions that have an active partnership with μLearn. They are not students moving through the learner progression. They enter the ecosystem through the **Faculty Track** a separate entry point specifically for educators.

### <mark style="color:$primary;">What Enablers Do</mark>

Enablers hold the ecosystem together at the campus level between formal student leadership layers. They:

* Run Learning Circle sessions for students
* Support IG Leads in task curation and validation
* Mentor newer learners informally
* Coordinate campus-level activities alongside Campus Leads
* Bridge communication between learners and leads
* Connect syllabus content to real-world proof-of-work opportunities

### <mark style="color:$primary;">Community Responsibilities</mark>

* Maintain a **welcoming, inclusive environment** in their spaces
* Identify and surface **struggling learners** before they disengage
* Recognise and celebrate **peer contributions** publicly
* Resolve minor conflicts at the community level before escalation

### <mark style="color:$primary;">Learning Responsibilities</mark>

* Stay current in their domain Enablers cannot lead what they don't understand
* Complete at least one Learning Circle per cycle as a participant or facilitator
* Share knowledge actively through sessions, documentation, or peer review

### <mark style="color:$primary;">Operational Responsibilities</mark>

* Support event logistics and coordination when needed
* Maintain accurate records of LC participation and outputs
* Report community health signals to IG Leads or Campus Leads

### <mark style="color:$primary;">The Art of Teaching Connection</mark>

Enablers are the primary audience for μLearn's **Art of Teaching** program a faculty enablement initiative that helps educators connect syllabus content to real-world applications and proof-of-work pedagogy.

The goal: transform the syllabus from a checklist into a living map. Connect every topic to why it matters not just for exams, but for the real world.

→ To understand the Art of Teaching program, go to [**Section 9 - Initiatives**](/initiatives.md)


---

# 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/roles-and-responsibilities/enabler.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.