> For the complete documentation index, see [llms.txt](https://docs.nuvolos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nuvolos.com/tutorials/tutorials-for-students/submitting-your-first-assignment.md).
# Submitting your first assignment
**What you will achieve.** \
By the end of this tutorial you will have located your first assignment, opened the assignment files in your application, completed the work, handed it in before the deadline, verified the submission, and reviewed the feedback your instructor sends back.
**How long it takes.** \
About 15 minutes for the submission flow itself, plus the time you spend doing the actual coursework and the time your instructor needs to grade.
**What you need before you start.** \
You should have completed your first tutorial - that is, you have accepted your invitation, you can navigate to your course, and you can start the application your instructor set up. You also need an active assignment from your instructor.
{% stepper %}
{% step %}
### Step 1 - Find the assignment
When your instructor creates an assignment for the course, it shows up in two places. Pick whichever is convenient.
* On the space overview dashboard - when you open the space, you will see the assignment listed.
* In the assignment view - click the assignment icon on the sidebar. This is the more detailed view: it shows submission deadlines, whether you have already submitted, and gives you the submission action when the hand-in is still open. The countdown color goes from red to green to indicate how much time is left.
Click the assignment to open it. You will see the files that are part of the assignment.
{% hint style="success" %}
**Checkpoint**
The files of the assignment are [distributed](/concepts/distribution.md) to you by the instructor. They appear in your application as regular files - you can open and edit them just like any other file. The deadline countdown should be visible in the assignment view.
{% endhint %}
{% endstep %}
{% step %}
### Step 2 - Work on the assignment
Open the application your instructor set up and navigate to the assignment files. Work on them as you would any other file.
Once you are satisfied with your work, save all the files in the application before moving on to the next step.
*Tip: Take a snapshot of your instance before submitting. That way you have a recoverable copy of your final draft if anything goes wrong.*
{% hint style="warning" %}
**Important - keep file names and locations identical**
To make submission simple, Nuvolos hands in the files that are part of the assignment automatically. You cannot manually "select" files to submit - every file in the assignment description is submitted automatically to the instructor.
This means if you worked on the material offline and want to bring it back in, you must move your solution to the exact same folder with the exact same name as you received it on Nuvolos. Otherwise the submission protocol will not find the file to submit.
{% endhint %}
{% endstep %}
{% step %}
### Step 3 - Hand in the assignment
To hand in:
1. Click the assignment on the dashboard, then click the Hand-in button on the top right of the dialog. Alternatively, open the assignment overview and use the Hand-in button under Actions.
2. Choose a hand-in identifier. This is what your instructor will see as the title of your submission. If you are uncertain what to use, ask your instructor - usually it is your university email address, a unique university identification number, or similar.
3. Confirm the submission.
{% hint style="warning" %}
**Submission rules**
All files in the assignment must exist at submission time - otherwise the submission will fail.
The total combined size of files and folders cannot exceed the hand-in limit. It is your responsibility to remove unneeded files from the submission folders. The system rescans file and folder sizes each time you try to submit.
{% endhint %}
{% endstep %}
{% step %}
### Step 4 - Verify the submission and resubmit if needed
After handing in, the submitted files appear in the hand-in area as read-only copies. It is recommended to check the hand-in area after a submission to make sure all files were submitted with the right version. You cannot modify the files there, but you can download them to verify.
To open the hand-in area from your application, navigate to:
```sql
Assignments > handback > [assignment_name] > [handin_id]
```
You can submit multiple times for the same assignment from the same instance until the deadline has passed. The instructor will only see your latest hand-in and will grade this version. This is true even if you use different identifiers for the different submissions, or if multiple users submit assignments from the same instance - one instance can have only one gradable submission, the latest one.
{% hint style="success" %}
**Checkpoint**
You should see your hand-in identifier listed in the assignment view, and the submitted files visible (read-only) in the hand-back area. If anything is missing, you still have time before the deadline to fix it and resubmit.
{% endhint %}
{% endstep %}
{% step %}
### Step 5 - Review feedback when it arrives
Once the instructor has reviewed your work, they will enable you to see the hand-back version of the files. To review:
1. Click the assignment tile to open the assignment view.
2. Look at the Handback tab. Your grade is shown there.
3. Review the corrected version of your files, listed under the Handback tab. These files are read-only for students; you can download them from the Actions column.
If you prefer to review the corrections inside the application, first stop any running applications, then click the Review Corrections button from the assignment dialog. The application will open with the corrections in:
```sql
Assignments > handback > [assignment_name] > [handin_id]
```
{% hint style="info" %}
**When feedback isn't visible yet**
You will only see feedback in the handback folder if the teacher has made handbacks available. Only the latest hand-in will be graded.
{% endhint %}
{% hint style="success" %}
**You're done**
You have completed a full assignment cycle: locate the assignment, work on the files, hand in, verify, and review feedback. The same flow applies to every assignment in your course — and you can resubmit any number of times before the deadline.
{% endhint %}
{% endstep %}
{% endstepper %}
#### Where to go next
* For the full reference of submission rules, the hand-in area structure, and feedback flow, see [How-to › Complete and submit assignments](/how-to-guides/workflows-for-students/working-on-assignments.md).
* If your course uses GPU-enabled applications, see [How-to › Collaborate and use special resources](/how-to-guides/workflows-for-students/working-with-a-gpu-in-a-course.md).
* To understand the model behind assignments and feedback, see [Concepts › Snapshots, distribution, and states](/concepts/distribution.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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.nuvolos.com/tutorials/tutorials-for-students/submitting-your-first-assignment.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.