Update SecurityModel.md

SecurityModel.md

@@ -16,11 +16,13 @@ only have a single update event every few minutes, we can authenticate only as n
 Currently the only exposed actions that require authentication are Editor-based ones, so we aren't assigning roles or having granular permissions.
 
 Actions available via Thrimshim are:
+* Unauthenticated Actions
   * `get_row`: Return a single row from the database by ID. Unauthenticated.
   * `get_all_rows`: Return the entire events table (or specific subsets of it), for building dashboards. Unauthenticated
-* `update_row`: Updates row in the Events table. Authenticated and limited to Editors and Admins (who can update different sets of rows). Authenticated.
+* Authenticated Actions
-* `manual_link`: Override the `video_link` field in the Events Table, in case of a manual upload. Authenticated.
+  * `update_row`: Updates row in the Events table.
-* `reset_row`: Clear `state` and `video_link` columns and reset `state` to 'UNEDITED' in Events table. Authenticated.
+  * `manual_link`: Override the `video_link` field in the Events Table, in case of a manual upload.
+  * `reset_row`: Clear `state` and `video_link` columns and reset `state` to 'UNEDITED' in Events table.
 
 ### Admin Access
 Node admins will connect directly to the database via third party tools (such as pgAdmin) for tasks such as adding members or manually overwriting the Events table.
@@ -30,5 +32,6 @@ Node admins will connect directly to the database via third party tools (such as
 #### Members Table
 
 columns     | type                | description
--------------------------- | ---------------------------------- | -----------
+------------| --------------------| -----------
-`user_email`               | `TEXT NOT NULL`                    | The email account used for the member's Google sign in.
+`email`     | `TEXT NOT NULL`     | The email account used for the member's Google sign in. (Primary Key)
+`name`      | `TEXT NOT NULL`     | The public username of the user (for administration purposes)