> 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/how-roles-work-in-mlearn.md).

# How Roles Work in μLearn

Roles in μLearn are earned, not assigned. They can be held concurrently. They come with real responsibilities not just titles. Find your role below and go deep.

Roles in μLearn work differently from most systems.

They are **earned -** through Karma, community trust, demonstrated contribution, and in some cases a formal assessment. You don't apply for most roles. You grow into them.

They are **concurrent** - a learner can be a Contributor and an IG Lead simultaneously. Roles are not stages you leave behind. They are responsibilities you add as you grow.

They are **track-based** - different roles belong to different tracks. Your track depends on who you are and how you entered the ecosystem.

### <mark style="color:$primary;">The Four Tracks</mark>

<mark style="color:$primary;">**Student Track**</mark>\
For learners moving through the ecosystem in any combination, at any pace.

* [**Learner**](/roles-and-responsibilities/learner.md) - everyone starts here
* [**Contributor**](/roles-and-responsibilities/contributor.md) - active community builders
* [**IG Lead**](/roles-and-responsibilities/ig-lead.md) - domain stewards
* [**Campus Lead**](/roles-and-responsibilities/campus-lead.md) - node operators
* [**Mentor**](/roles-and-responsibilities/mentor.md) - guides for the next generation

<mark style="color:$primary;">**Professional Track**</mark>\
For industry experts and domain professionals entering directly.

* [**Mentor**](/roles-and-responsibilities/mentor.md) - industry practitioners bringing real-world expertise
* [**Think Tank**](/roles-and-responsibilities/think-tank.md) - Subject Matter Experts who define and validate domain standards

<mark style="color:$primary;">**Faculty Track**</mark>\
For educators and faculty members from partner institutions.

* [**Enabler**](/roles-and-responsibilities/enabler.md) - faculty members bridging academia and μLearn

<mark style="color:$primary;">**External Track**</mark>\
For organisations engaging with μLearn as partners.

* Partner → [ **Partner Engagement**](/partner-engagement.md)

Every role is earned. Every role has a scope. Every role has a limit. Find your role. Go deep.


---

# 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/how-roles-work-in-mlearn.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.