devdocs/specs/core-roles.txt

@@ -23,6 +23,24 @@ For example a SubContractorLimited has the change right to a workorder, but in f
 
 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 
+** LIMITED ROLES ACCESS RIGHTS PLANNING **
+As of jan 2020 just trying to determine what the limited roles do as they are the least clear, here is some thinking on that:
+	- Do I need all the limited roles or are some redundant
+		- My thinking currently is it could be too complex for people to understand unless it's very clear what the dividing line is and in many cases people probably won't care about the limited roles / overthinking it
+			- some people want to set every last little thing but are we selling to those people or to people who just want to get shit done
+			- Many people just want the ability to not show private info and I have pretty good handle on that like hiding costs, client lists etc
+			- How many of oru customers will have a junior dispatcher or junior inventory person?
+	- Even if this isn't perfect I need to start with something and can build on it later, so keep in mind TTM and simpler is better up to a point
+	- No need to figure everythign otu at this point, it's easier to work with actual features down the road and restrict more then
+	- Issues is mainly to do with what the limited roles are all about and where the dividing line for features will be
+    - MAYBE the way to think of this is that the limited roles are all basically READ ONLY versions of the full roles
+        - This satisfies the need for office people to be able to look shit up but not break it by changing it
+    - CURRENT RESOLUTION  TO THIS: just go ahead and code it now
+        - I have a pretty clear understanding of the full roles
+        - Work out the Limited roles later when I have actual features to limit and can see it in action
+        - Code it so that this is kept in mind so it's not a bitch to go back in limit later
+==================================================
+
 LISTS UNDER LIMITED ROLES
 If a user *can* potentially view or edit an object type then that object's list will display, if certain fields should be restricted then they will be via business rules when the record is opened.
 So in theory lists should not show stuff that a user has no rights to see, so some columns need to be restricted for those users when the list is delivered by the server
@@ -88,7 +106,7 @@ No rights, not settable, just for internal usage in code
 ### BizAdminLimited
 Intended for a business administrator / supervisor who wants to monitor the business, kpi, reporting etc, but doesn't actually get to change anything.
 Suitable for the "big boss" who isn't trusted to make actual day to day decisions but can review anything.
-
+NOT FULLY FLESHED OUT THIS CAN ALL CHANGE
 **RIGHTS**
 - Read only access to everything (except OPS stuff)
 - Full access to management reporting, KPI etc, but can't change them substantially, just sort, filter etc.
@@ -111,6 +129,7 @@ Basically the v7 manager account stuff with full rights to everything other than
 
 ### DispatchLimited
 see roles.odt for more info
+NOT FULLY FLESHED OUT THIS CAN ALL CHANGE
 - Intended as the junior dispatcher account, where they can help with day to day but not change anything big or see any private data
 - Can create workorder
 - Can add users to workorder / schedule
@@ -132,6 +151,7 @@ see roles.odt for more info
 
 ### InventoryLimited
 see roles.odt for more info
+NOT FULLY FLESHED OUT THIS CAN ALL CHANGE
 NO PO functionality except maybe able to receive?? To be determined
 View inventory, adjust inventory
 creat parts, assign vendors etc (dispatcher comes to them for new parts to be created)
@@ -164,6 +184,8 @@ see roles.odt for more info
 ### TechLimited
 see roles.odt for more info
 - CONSUMES A LICENSE
+NOT FULLY FLESHED OUT THIS CAN ALL CHANGE
+- Isnt this basically a subcontractor though?
 - More rights than a subcontrator but less than a full tech, cannot see sensitive data
 - Can't schedule themselves only add labor
 - Can make entries into existing workorders, add rows to existing areas in the workorder but can't add a new area or create a new workorder
@@ -175,6 +197,7 @@ see roles.odt for more info
 ### SubContractorLimited
 For filling out labor on workorders but not seeing any details of the workorder
 Like a tech limited but more limited.
+NOT FULLY FLESHED OUT THIS CAN ALL CHANGE
 ** Essentially the only purpose of this is to allow them to enter labor on a pre-existing workorder but really see almost nothing on the workorder except the bare minimum to enter labor
 They can see only where they are scheduled in the schedule form, no client name, nothing of any detail at all, just work and enter it.
 see roles.odt for more info
@@ -193,12 +216,25 @@ see roles.odt for more info
 ### OpsAdminLimited
 Like ops full but for read only and simle maintenance or watching / observing when issues
 A role you'd give an office person with no tech background but who is tasked with backup or looking at logs when things go wrong
+backup but can't restore
+view logs, call ops full (I.T.) when issue arises
 
 ### OpsAdminFull
 Any major db change like restore, importing etc.
 backup, troubleshoot, dashboard of throughput, db administration, all the stuff needed to keep RAVEN up and running and monitor any issues in operations of it, 
 nothing to do with business stuff or actual business data
 
+### SALESFULL
+Makes QUOTES
+View and create clients?
+Turn quote into workorder? (that implies scheduling rights, sb dispatcher job)
+Maybe they approve the quote for service then a service manager does the actual booking!
+
+### SALESLIMITED
+(basically a read only sales full)
+Views quotes, can't change them?
+View customers can't change them
+
 ************************************************************************************************************************************************************
 
 

server/AyaNova/biz/AuthorizationRoles.cs

@@ -44,13 +44,18 @@ namespace AyaNova.Biz
         OpsAdminLimited = 8192,
         ///<summary>OpsAdminFull</summary>
         OpsAdminFull = 16384,
+        ///<summary>SalesFull</summary>
+        SalesFull = 32768,
+        ///<summary>SalesLimited</summary>
+        SalesLimited = 65536,
+
 
         ///<summary>Anyone of any role</summary>
         All = BizAdminLimited | BizAdminFull | DispatchLimited | DispatchFull | InventoryLimited |
         InventoryFull | AccountingFull | TechLimited | TechFull | SubContractorLimited |
-        SubContractorFull | ClientLimited | ClientFull | OpsAdminLimited | OpsAdminFull
+        SubContractorFull | ClientLimited | ClientFull | OpsAdminLimited | OpsAdminFull | SalesFull | SalesLimited
 
     }//end AuthorizationRoles
-//32768, 65536, 131072, 262144, 524288, 1,048,576
+     //, 65536, 131072, 262144, 524288, 1,048,576
 }//end namespace GZTW.AyaNova.BLL