Shaped around your university
Customisable software should fit the department using it: the identity, courses and rules that make the workspace yours.
Start with what your department needs
Use a shared core for the hand-in, then define the details that matter to your courses and academic process.
Your identity and academic structure
University and department
Use familiar names and terminology in the workspace.
Courses and assignments
Set up course labels, practical briefs and the deliverables students are expected to submit.
Student and group details
Define the identifiers and group information that need to accompany the work.
The rules behind the hand-in
Choose accepted submission formats, deadlines, late-work handling and marking totals. The preview lets you change these settings and see the student view update.
Submission formats
Accept a code file, require a ZIP archive or use a repository link for a larger project.
Deadlines and late work
Make the due date visible and define how work after that date should be handled.
Review requirements
Agree on marking scales, rubric requirements and the way students receive feedback.
Plan the details before rollout
Academic workflow
Which courses and cohorts are in scope? Who can publish assignments and review submissions?
Student access
How should students be identified, and what access arrangements does the university require?
Institutional setup
Agree on hosting, storage, retention, support and any connection to existing university systems as part of the implementation scope.