Assignments: create, publish & track

Assignments collects the tasks visible to the signed-in role. Search and filter the available workflow states, then use Cards or List as offered. A Student sees work made available within their academic scope, not hidden Draft tasks.

An authorized inline status selector updates a task without opening its full page. It is still a real server update and can fail if permissions or the record have changed. A successful state change is different from receiving a student's submission or entering a grade.

Create assignments from the correct academic context so the scope is unambiguous. Provide a clear title, instructions, total marks, workflow status, deadline where applicable and supporting attachments. Subject-, chapter- and topic-level tasks are separate records.

Use Draft while preparing work. Review the marks and deadline before publishing. Editing the deadline can change whether students may submit; uploading an attachment is subject to storage policy. A copied assignment arrives as Draft without its old deadline and must be reviewed before use.

Overview shows the assignment target, due date, marks, workflow status, instructions and attached files. Submission and evaluation counts describe separate steps. Students see their own progress while authorized staff see the task's permitted population.

Before submitting or evaluating, read the full instructions and confirm the task belongs to the intended subject or topic. Files open through the attachment links. A summary indicating that uploads are closed should be treated as a deadline/state restriction, not worked around with a shared login.

Reports separates submission rate, evaluation rate, average/own marks and awaiting-review counts. Result bands summarize evaluated outcomes; they are not automatic grades for unreviewed work. A valid score of zero remains an evaluated result.

Use the staff submission list to investigate who still needs evaluation. Students receive their own result context rather than the class-wide grade distribution. Curriculum status alone should not be changed to simulate a submission or assessment.

Assignment Discussion keeps questions and staff updates attached to the task. It does not count as an assignment submission. Use the upload or public submission form to deliver work, even if you discussed it in the thread.

Mention only available participants and keep private account or payment information out of comments. If instructions change, authorized staff should also update the assignment itself so the task remains the source of truth.

Open the existing assignment and use Edit when your role and permissions allow it. The form lets you review the title, instructions, marks, workflow status, deadline and supporting files. Editing the existing record is different from creating another assignment.

Review the effect on students before changing a published task. A deadline or status change can affect whether submissions are accepted. Wait for a successful save and check the refreshed Overview before telling students that a deadline has changed.