diff --git a/devdocs/specs/core-main-grids.txt b/devdocs/specs/core-main-grids.txt
index e443a194..e11dd520 100644
--- a/devdocs/specs/core-main-grids.txt
+++ b/devdocs/specs/core-main-grids.txt
@@ -39,12 +39,12 @@ Server
     - Grid lists need to know what their template is as more than one list might use the same template?
     - SERVER SENDS LIST OF COLUMNS
 			- The server needs to tell the client which columns are coming back with the list and what types etc so the client can just adapt to any template setting 
-            - column list has type of object behind each column if applicable so client can make hyperlinks
+            - column list has type of object behind each column if applicable and user has rights to open so client can make hyperlinks
     - SERVER SENDS DATA
         - Data in a standard for all grid lists json format, not based on set objects (I think I can do that, probably a hybrid object with JSON data)
             - Each row has each column as a object comprising of:
                 - Display value (the data to show, not formatted yet, that's up to the client)
-                - Optional: ID value (if the object is openable then this is the id to open for the client to put a hyperlink on that column)
+                - Optional: ID value (if the object is openable **** MUST CHECK RIGHTS ALSO HERE **** then this is the id to open for the client to put a hyperlink on that column)
                 - For example (wide list):
                     data:{
                         columns:{ {name:"lt_client_name",datatype:text,ayatype:client},{name:"lt_client_notes",datatype:text},{name:"lt_last_workorder",datatype:number,ayatype:workorder}}