devdocs/specs/core-roles.txt

@@ -5,17 +5,18 @@ From case https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1809
 RAVEN will replace security rights system of v7 with a role based system instead
 I'm using an int flags enum which means a maximum of 32 possible roles unless I bump it up to a long but don't really want to as this number will be thrown around the api a lot
 
-
-
-TODO: Fill this out as I code.
+ROLES set general accessibility to change or delete or read objects, however Business rules may further restrict on top of that.
 
 **DELETE RIGHTS***
-If you can modify an object you can delete an object
+If you can modify an object you can delete an object unless business rules say otherwise
+
+
+**LIMITED ROLES / BUSINESS RULES LIMITATIONS **
+(formerly self owned)
+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
 
 
-**OWNER LIMITED ROLES**
-Limited roles in some cases can create an object but can only edit or delete objects they created
-?? STILL BEING PLANNED OUT SEE BELOW AT BOTTOM ??
 
 ## ROLES