Private Job Reservation and Submission system

A user is required to login via Google oauth.
This user email is checked against a master file or DB.
A user can have up to three roles. T and E and admin (contains both T and E roles, and additional privileges)
A user can have a list of projects to do.
User will be given a landing page, allowing him to choose from his list of projects.
Admin will see all projects
When user enters a project page, he will see a table (taken from Google Spreadsheets/rest api, or a database)
there will be 7 columns.
1. An index (integers that don’t necessarily start from 1)
2. Involves 'T' users. It will show either:
a) another user name (if claimed or completed by someone else),
b) a tick, (if done by the logged in user)
c) a Reserve button (if no one has claimed this row)
d) a Done? button (if logged in user has claimed but not done it), linked to a script for verification
3.
A date which is populated after a Done? signal is sent (and verified)
4. Involves 'E' user. See Column 2.
Generally there is only one 'E' user
5. Involves 'E' user. See Column 3.
Generally there is only one 'E' user
6. Involves same 'T' user in Column 2. Details: See Column 2.

7. Involves same 'T' user in Column 3. Details: See Column 3.
8. A dropdown box with numbers ranging from 1-20
At the bottom of the table, if a Done? Submission returns an error message from the script, the Done? will not be successful. A pop up will indicate the error.

An Admin user will be able to change all columns with a dropdown.
Columns 2, 6: Choice of available ‘T’ users, including the admin’s name
Column 4: Choice of ‘E’ user, including the admin’s name
Column 3,5,7: Clicking on the date pops up a calendar widget for submission
There should be a submission button for the admin.

Admin should have an interface to add projects
In the project settings, Admin should have an interface to add user and roles, with additional text fields (comments, etc). Addition done by using their gmail addresses.