> 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/campus-chapter-playbook/working-with-faculty-enablers.md).

# Working with Faculty Enablers

While a single Lead Faculty Enabler is essential for initiating a chapter, the long-term sustainability and academic integration of µLearn depend on a multi-departmental support system.

### <mark style="color:$primary;">Building a Multi-Departmental Committee</mark>

* **Scalability:** As µLearn activities stabilize and gain momentum, the Lead Faculty Enabler should identify and invite other faculty members who are supportive of student-led learning.
* **Diverse Representation:** Efforts should be made to include faculty from various departments to ensure µLearn principles are not siloed but integrated into the broader academic culture of the institution.
* **Mentorship Circles:** These additional enablers form a core team of mentors who can guide specific Interest Groups (IGs) or specialized initiatives based on their departmental expertise.

### <mark style="color:$primary;">Strategic Advantages</mark>

* **Administrative Efficiency:** A larger circle of faculty supporters makes approvals for venue bookings, equipment access, and program alignments significantly faster and smoother.
* **Institutional Recognition:** A multi-departmental committee helps create a positive perception of µLearn across the entire institution, framing it as a complement to formal academics.
* **Accountability and Quality:** While the programs remain student-driven, a team of enablers can monitor planned activities to ensure they align with campus policies and maintain high standards of quality.

### <mark style="color:$primary;">A Culture of Collective Growth</mark>

* **Faculty Upskilling:** µLearn is not limited to students; faculty enablers are encouraged to attend IG sessions, join learning circles, and stay updated with emerging industry trends alongside their students.
* **Collaborative Environment:** When faculty and students learn and grow together, it enriches the chapter and fosters a more impactful and supportive innovation ecosystem on campus.

### <mark style="color:$primary;">The Unlearn Network</mark>

It is mandatory to ensure that the Lead Faculty Enabler joins **Unlearn** the global µLearn campus enabler family. This connects your campus faculty to a wider network of enablers across all µLearn chapters.

{% hint style="warning" %}
Manual Intervention: Faculty Enabler onboarding to the Unlearn Network is managed by the µLearn Foundation. Contact <campus@mulearn.org> for support.
{% endhint %}

To understand the full Execom structure and the Enabler's role within it, go to [**Campus Execom Structure**](/campus-chapter-playbook/campus-execom-structure.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/campus-chapter-playbook/working-with-faculty-enablers.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.