devdocs/specs/core-roles.txt

@@ -10,6 +10,10 @@ ROLES set general accessibility to change or delete or read objects, however Bus
 **DELETE RIGHTS***
 If you can modify an object you can delete an object unless business rules say otherwise
 
+**SEE NAME / PICKLISTS ***
+    - Not sure if correct but for now assuming anyone can read the name of any object and that the UI will exclude them by biz rule if they aren't supposed to see something
+    - this does mean a subcontractor could use the api to fetch a list of customers outside of the client though...hmmm..
+    
 
 **LIMITED ROLES / BUSINESS RULES LIMITATIONS **
 (formerly self owned)
@@ -17,7 +21,7 @@ In some cases business rules may further restrict what a user can do.
 For example a SubContractorLimited has the change right to a workorder, but in fact the workorder itself has business rules that limit that drastically down to almost nothing but a single area entry in labor
 
 =-=-=-=-  HOW TO HANDLE EDIT OWN PLANNING =-=-=-=-=-
-- EditOwn is really not about editown it's about supporting a user who is not supposed to see any data other than the bare minimum in order to fill out workorders
+- EditOwn IS DEPRECATED FROM ORIGINAL PLAN is really not about editown it's about supporting a user who is not supposed to see any data other than the bare minimum in order to fill out workorders
 	- Make it a business rule(s) instead in the areas of workorders and anything specific
 	- Get rid of edit own rights code entirely