> For the complete documentation index, see [llms.txt](https://docs.lamsfoundation.org/lams/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lamsfoundation.org/lams/tools/branching/student-selection-branching.md). # Student Selection Branching ## **Using student selection for branching** Using this branching type, you -**the teacher, get to create branches and then allow students to select which branch they want to take.** Additionally, you can allow students to take one or more branches. ### Creating student selection branching This pushes the decision as to which branch to take to the students. So as a teacher, you can offer different learning patch (branches) and then let the student select which one (or more than one) to use. {% embed url="" %} Creating a branching where teachers allow students to select their own learning path {% endembed %} ### Student selecting learning path in lesson Once a student reach the branching starting point, then student is prompted to select a learning path. If the teacher allows the students to select more than one learning path, then on completion of the first selected, then the student will be able to select another one. --- # 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.lamsfoundation.org/lams/tools/branching/student-selection-branching.md?ask=&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.