• ✨ We have bumped the server to PHP 8.2

• ✨ Allowing job reallocation and re-opening.

• ✨ Job allocation screens now correctly assign times for people with visa restrictions
• ✨ It also checks contract end dates. Oh yes, and both these changes happen for auto-reallocation too.
• ✨ You can allocate additional workers to a role if required with the new "Allocate more workers button".
• ✨ Workers can sign in and out via their accounts.
• ✨ Method of timestamp creation now shown on the finalisation screen.
• 🐛 Workers shifts now aren't double counted at sign out for visa hours restrictions.

• ✨ There is a new screen for workers wanting to join schemes. You as admins can choose what schemes can be joined from each link, as well as setting a period of validity
• ✨ Going with the above, schemes cannot now be directly joined, sorry! You have to make a process workflow for each scheme with the steps required.
• ✨ Right to work workflows have been overhauled, with new steps which automatically send contract emails to workers.
• ✨ New workers now get a welcome email, and not just a password. Better.
• ✨ Allocating workers is now different in two ways:
  • You now have to select the checkbox on the left, rather than the right. This will allow selections to be carried from page to page. Snazzy.
  • You can now allocate additional workers to the same job if it has been re-opened without affecting the original allocation
• ✨ You can now see people from other teams on your staff list for events. Your team is at the top, naturally!
• 🐛 Validation now works on MS Edge
• 🐛 Emails can be sent by staff, and not just admins.
• 🐛 The payroll view actually works!

• ✨ You no longer have to download timesheets and submit them manually. Simply finalise the event, then off you go! Payroll will now do the rest.
• ✨ HR can approve Tier 4 student shifts for compliance reasons before they are paid.
• ✨ The worker page is completely different, but now you can email them!
• ✨ Emailing has got a lot simpler, and you can also see all emails sent to a worker.
• ✨ Workflow steps can now send an email on completion.
• ✨ New users now get a fancy email.
• 🐛 When you copy a job, it will now not change the advertising date if that is in the future.
• 🐛 You no longer have to double approve events if they don't have pre-approval.
• 🐛 Lots of other little bugs have been squashed.

• ✨ Info Buttons exist!
• ✨ We have a new footer. Check it out.
• ✨ Email templates, yes they're a thing!
• ✨ Prepare for automated payroll... so you can no longer download an event timesheet.
• ✨ Budget Approval. Starting immediately, all events will need approval to be advertised and finalised.
• ✨ Oh, and emails are now sent asynchronously, that should speed up the page loads for you!
• 🐛 Tier 4 now works Monday-Sunday
• 🐛 You can now make a group a faculty or a scheme from the groups page.
• 🐛 Lots of little bugs have been squashed.

• ✨ You can now advertise and book workers to jobs.
• ✨ We have a new footer. Check it out.
• ✨ We have completely rebuilt the objects driving tha back end to make the site more stable.
• ✨ Tier 4. Workers with a T4 visa expiry date set will now have their hours tracked and prevented from working over limits
• 🐛 Oh, and we have fixed the fact you can't access the documentation. Soz.

• ✨ There is a new worker page! You can now edit worker user names, and reset thier passwords. This is all in preparation for advertising and booking coming in the next version.
• ✨ Workflow inboxes are now a thing. This allows a single step of a workflow to be seen in isolation and completed. Speak to a system admin if you think this would be good for you!
• ✨ Workflows can now be used to add groups and other workflows (thats a bit meta...), but this should make them more flexible to what you need.
• 🐛 You can now filter by student not in groups, and send links to a filter for others to use.
• 🐛 Workers are now made active and inactive by workflows only.
• 🐛 The system doesn't have any issues with emoji anymore. Go crazy! 🎉
• 🐛 We've started flagging if its a new feature or bug fix in this page!
• 🐛 Oh, and there is now a global setting for the email address. Much better.

• There is a new events page! The new list allows you to edit and add events easier.
• It looks more like the workers list, and should be faster.
• You can now list multiple staff as responsible for an event
• Worker edit pages open in a new window by default. Once you have edited the worker, close the tab to resume with the list.
• There is a beta version of a new page for people who are still signed in. Give it a go and feedback
• Loads of bug fixes!

Password resets are now sent by email (mostly), along with new user creation. You can now see how many students are present at your event, and QR codes can be generated for logins screens. We have also changed to using Moment.js to handle dates, as the old method was causing troube with timezones.

Pay grades can now be created or amended. They specifically cannot be deleted as that could cause chaos

Digital Sign In now works! Students can sign in to their shifts, sign out, and then create a timesheet for any shift worked. A break of 30 minutes or more is considered a break, less than 30 minutes is a shift continuation.

In order to better meet the requirements of the GDPR, we now have access logs!!

Migrated to PHP 7.2, and switched password hash algorithm too. All users will have to reset their passwords.

We can now create and delete users without having to use SQL. Well done us! Users can also change their own passwords,but still need to see an admin if they have forgotten it!

User sessions now time out after 30 minutes of inactivity, password resets are handled in a more secure manner and all user updates are handled by Admin users.

Now you can amend details of users and reset their passwords! Yay!

Get in contact with the System Admins to get your account today! If you don't know who the system admin is, you probably shouldn't have access!

This is the first version put online to https://studentworkers.uea.ac.uk. Session cookies are used for user accounts, however as these are only used for authentication, then we have no need to ask permission of users.