As mentioned earlier, students will be blocked from submitting if they have already viewed the assignment solution. There are other ways to restrict students' submissions.

By adding a submissionLimit attribute to the root <assignment> element, you can specify a maximum number of attempts each student can make. For example:

<assignment notify="cs361@cs.odu.edu" submissionLimit="3"> 
  <title>CS361: Keeping Your Distance</title> 
   ...
</assignment>

This says that students will be allowed to submit a total of 3 times. If no limit is given, then students are permitted to resubmit an arbitrary number times. If you wish entirely prohibit resubmissions, therefore, give a submissionLimit of 1.

This limit is implemented by checking the submissions directory to see how many copies of the assignment have been submitted by the logged-in student. If you wish to override this limit for a particular student (without raising the limit for everyone), you would need to manually remove that student's most recent submission from the submissions directory.

If a grades directory has been specified, then submission can also be blocked by the presence of an arbitrary file in the grades directory. Add an attribute block that names the file to be checked for. If that file exists in a student's grade directory, then that student will be blocked from submitting again. For example,

<assignment notify="cs361@cs.odu.edu" submissionLimit="3" block="gradeReport.txt"> 
  <title>CS361: Keeping Your Distance</title> 
   ...
</assignment>

This says that students can submit up to 3 times, but that once the assignment has been graded (a gradeReport.txt file exists) then students will be blocked from further submissions (even if they have not used up all three attempts).