> 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/doku/student-view.md).
# Student view
When a student opens the doKu activity from the lesson, they see **title** and the **description/Case** if your entered during [authoring](/lams/tools/doku/create.md).
If you added a template as part of the document, they will get started editing with the text you added
## Working on the document
Students type directly into the shared document. Changes are saved automatically as they work.
**Real-time collaboration:** When students are in the same team (a grouped activity), everyone editing at the same time sees each other's changes immediately. Each person's contributions appear in a **different colour**, so it is easy to see who wrote what.
**Individual activities:** If the activity is not grouped, each student works on their **own** document. There is no co-editing with classmates in that case.
{% hint style="info" %}
**Want only one person per team to type of behalf of the team?**
You can enable this option when [authoring](/lams/tools/doku/create.md), just set the activity so only the leader of the team can edit. Note that all other students can see what the leader is typing, but only the leader can type (see [details](#use-leaders-from-select-leader-tool)).
{% endhint %}
#### Feedback from the lecturer
At any given time, while the students are working on the document, you as lecturer might send them feedback.
You can send feedback immediately, which will appear directly above the student's work. Alternatively, the feedback can be sent after the students finish their answers via email, in case you want to provide after-lesson feedback. The email is directed to all students in the team.
This is separate from AI Feedback Coach feedback; a lecturer may send their own written feedback regardless of AI settings.
### Finishing the activity
When the student is done, they click:
* **Next Activity** — if there are further activities in the lesson, or
* **Finish** — if this is the last activity in the lesson.
With default settings, **Lock when finished** is off. Students can return to the activity later and continue editing, unless the lesson has already moved them forward.
## How different optional settings change the doKu experience
Each subsection below describes what changes compared to the default experience above.
### Document Base (Template)
**What changes:** If you as leacture added a Document Base, then the collaborative document opens with that content already in place: headings, prompts, bullet points, or partial text, instead of a blank page.
This gives students a template or structure to work from rather than starting from scratch.
### Lock when finished
**When enabled, these are the changes**
* Before finishing, students see a warning that they will not be able to edit the document after they complete the activity.
* After they click **Next Activity** or **Finish**, the document becomes **read-only**. They cannot add or change content if they return to the activity.
### Enable burning questions
**What changes:** While working on the document, students who can edit see a **Burning questions** button. They can submit a question or request for clarification, which is sent directly to their lecturer. A confirmation message appears when the question is submitted.
**Default comparison:** With the default (off), there is no way to send questions from within the activity.
{% hint style="info" %}
**Note:** During Gallery Walk, burning questions from across the class may be visible to all students if the lecturer has configured that activity accordingly.
{% endhint %}
### Use leaders from Select Leader tool
**When enabled, these are the changes:**
* **Only Team leaders can add/edit the document** on behalf of their team.
* **Other team members** see the document in read-only mode. They can watch the leader's work in real time but cannot type.
* Non-leaders see who the team leader is displayed on screen.
* The **Next Activity** / **Finish** button stays disabled for non-leaders until the leader completes the activity (or the leader's response is finalised).
**Default comparison:** With the default (off), every member of the team can edit the document.
**If no leader has been chosen yet:** Students see a waiting screen asking them to wait until someone becomes the group leader and enters the activity.
### Shared pads
**When the lecturer is using Shared Pads,** this means that documents are carried across various doKus in the lesson.
The document is linked to that ID rather than being unique to this activity alone. If the lesson contains **multiple doKu activities** using the same Shared pad ID, students continue working on the **same document** across those activities.
**Default comparison:** With the default (off), each doKu activity has its own separate document.
### Time limits
{% hint style="warning" %}
Time limits might not just apply at authoring but also when the lecturer is monitoring the activity
{% endhint %}
#### Activity (synchronous)
**If enabled:**
* A **countdown timer** appears while students work. It turns red when 30 seconds or less remain.
* The timer starts when the **first student** enters the activity. **All students** share the same deadline.
* When time runs out, editing is blocked. Students see a message that time is over and no further editing is allowed. The page reloads shortly after.
The lecturer can adjust or extend time during the lesson from the monitoring screen.
#### Individual students (asynchronous)
**If enabled:**
* Each student gets their **own** countdown, starting when **they** enter the activity.
* The timer behaves the same way (countdown display, red warning near the end,
**Typical use:** Self-paced or online cohorts where students start at different times.
## AI Features
### AI Feedback Coach
After students submit their answer -regardless if it was individual or as a team, **LAMS AI will compare and contrast the answer** of the student(s) **against the model answer and learning outcomes**.
**By default the AI feedback is not display to students untiil it is reviewed by the lecturer.**
However, **if the option for Display AI-generated feedback immediately** on submission **is ON**, then **students see an AI-feedback analysis** of their submission, including strengths and areas for improvement **without waiting for lecturer approval**.
### AI Personas: Chat with AI persona
If the lecturer **set up chat with AI persona** and configured the persona, students can open a **chat with an the said AI persona** while working on the document.
Students interview an AI persona: Graham Bell
The persona knows the activity is aware of the educational outcomes that are expected from the students along with customisation the lecturer added, but it **does not** have access to what students are currently writing in the document.
Students are expected to take notes on their document and can switch between the document view and the chat view.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.lamsfoundation.org/lams/tools/doku/student-view.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.