Directors must be able to manage teacher accounts

[josepostiga]

Scenario

As a Director
I should be able to access teacher accounts
So that I can create/update/delete teachers

Description

In order to get users into the system, and since this type of software doesn't work well with public registrations, it needs another authenticated account to start inviting teachers into it. That's one of the main purposes of the Director account. By creating new teacher accounts, the system will send out an invitation to the given email registered. This email is intended for the new teachers to validate their address, set an initial password, and then login into the system.

When updating the teacher accounts, the email and password properties shouldn't be updatable. The email property, however, must be visible, though, to allow for visual confirmation of the information inputted.

The deletions should be soft, meaning that no record will actually be removed from the system but, instead, a date property dedicated to simulating deletes must be filled when that action is executed.

Database and schema information

Two new account types should be accepted in the user table: TEACHER and HEADTEACHER. The email_verified_at column should be kept null until the email validation link is clicked.

Don't forget to confirm that a deleted_at column exists, as teachers can be soft-deleted.

Additional requirements

Only after the email validation link is clicked, is that the new teacher account can be used to login into the system.

The HEADTEACHER account type will be used to differentiate access permissions between teacher accounts, as this type should allow access to more sensitive information, like parents' information and disciplinary actions taken for a student.