devdocs/specs/core-roles.txt

@@ -37,6 +37,7 @@ Basically the v7 manager account stuff with full rights to everything other than
 
 **RIGHTS**
 - Full access to all AyaNova objects with the sole exception of OPS related stuff
+- ONLY role that can make a user or change a user's roles
 - Grants roles to other users
 - Licensing
 - Business related configuration settings
@@ -46,16 +47,46 @@ Basically the v7 manager account stuff with full rights to everything other than
 - NO Operations rights at all so no setup, or troubleshooting logs or technical details 
 
 ### DispatchLimited
+see roles.odt for more info
+- 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
+- NO create clients
+- No areas of workorder that are not directly related to scheduling
 
 ### DispatchFull
+see roles.odt for more info
+- Intended as the role for the person managing a group of techs and scheduling, pre-filling in workorders etc
+- Create workorder
+- Create clients
+- Create vendors
+- Can see anything related to scheduling and conveying service
+- Not necessarily the service manager who would have multiple roles like InventoryFull and DispatchFull
+- Schedule anyone
+- View and edit any area of any workorder with possible exception of profit and loss stuff or any strictly BIZ functionality
+- Does not have inventory rights to make inventory changes like creating parts
+
 
 ### InventoryLimited
+see roles.odt for more info
+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)
+NO dangerous or biz affecting rights
 
 ### InventoryFull
+see roles.odt for more info
+Same as inventory limited but with all the PO related stuff
+Also can fully change and create warehouses
+Create vendors
+
 
 ### Accounting
+see roles.odt for more info
+- Create vendors
 
 ### TechFull
+see roles.odt for more info
 - consumes a license
 - Can create their own workorders and schedule themselves on them but can't schedule others, that's dispatch job
 - Some areas of workorder are still not availble if they are related to other roles such as accounting etc
@@ -64,25 +95,39 @@ Basically the v7 manager account stuff with full rights to everything other than
 - Can create client
 
 
+
 ### TechLimited
+see roles.odt for more info
 - CONSUMES A LICENSE
 - 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
-
+- Can only see their own workorders, no one elses
+- No access to any costs or business data of any kind
 
 
 ### SubContractorLimited
-Like a tech limited but more limited in some ways to be determined (mostly not seeing any private data).
-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
+For filling out labor on workorders but not seeing any details of the workorder
+Like a tech limited but more limited.
+** 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
+can only add themselves as a labor entry, not much else unless it proves necessary.
+For a tech/subcontractor that is not trusted with company information including even client name – i.e. just given the work to perform and enter details about that work, but doesn't need access to anything else
+Can't select new parts only uses existing ones
 
 ### SubContractorFull
+Same as limited except can also see the client name and address and can select parts and other things to add to workorder but not see any details about those things outside the wo view
+see roles.odt for more info
 
 ### ClientLimited
 
 ### ClientFull
 
 ### 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
 
 ### 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
 
@@ -91,6 +136,9 @@ nothing to do with business stuff or actual business data
 =-=-=-=-  HOW TO HANDLE EDIT OWN PLANNING =-=-=-=-=-
 
 	- EDIT_OWN: HOW TO HANDLE PROPERLY??
+		- PROPOSED SOLUTION: 5/16
+			- Edit own is actually unnecessary, it's more about a specific business rule applicable to a single scenario of a techlimited or subcontractor or client user
+
 		- NOTES FROM 5/14/2019
 			- Here are the most important characteristics to consider:
 				- 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
@@ -104,8 +152,7 @@ nothing to do with business stuff or actual business data
 					- People are most concerned with hiding profits and private competitve data from subcontractors
 				- Is this the best way to handle the intended use-case which is to have a tech user with limited rights to only see their shit and fill out workorders?
 				- Is this also a way to handle client users?
-				- What happens when a user is only allowed to see their own objects and has to choose a labor that they didn't create?
-					- Picklists are exempt from rights shit though so if just picking not an issue, it's editing that's the issue.
+