> 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/group-based-branching.md). # Group-Based Branching ## **Using groups for branching** Using this branching type, you -**the teacher, get to map different students groups/teams into each branch.** When creating a branching that uses groups, then you can assign each group to a branch. ### Creating teacher's choice branching The way you create different learning pathways or branching, it is always the same. However, the decision on how students are allocated or routed to each branch is different. This short video shows how to create a set of branches and then choose the option for teacher's choice. {% embed url="" %} Creating a branching where teachers assign teams to different branches {% endembed %} During the lesson, you -as teacher, don't need to do anything as the teams have already being assigned to branches at authoring time. --- # 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/group-based-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.