ayanova/devdocs/todo.txt

@@ -12,6 +12,24 @@
 
 
 
+
+
+todo: Customer access
+	- global settings
+		- viewing workorder list is separate from viewing wo reports so needs separate right as well
+		- reports in section just under workorder list as they go together
+			- has default report that is offered to all if set
+			- has either a collection or limited set of "Only if Customer tagged with..." and report selected combo
+	- When customer renders a report the client doesn't send which report, the server looks it up at render time based on tags etc
+		maybe it's own render route??
+	- When customer logs in, server sends flag indicating *if* they can do wo reports or not, no need to set which report or tags or whatever, just that it's capable
+	
+
+
+
+
+
+
 OUTSTANDING MAJOR AREAS TO BETA
 	
 - Features	
@@ -27,7 +45,12 @@ OUTSTANDING MAJOR AREAS TO BETA
 		- Has pertinent cases
 		- ROLES need a completely full documentation or some way to view what is accessible for what maybe in code in the UI???
 		There is no clear ROLES guide and we need one for sure.  I like the idea of dynamically generated in the UI so we can change it and it's always accurate and 
-		useful for us to ref as well, should have done it long time ago.	
+		useful for us to ref as well, should have done it long time ago.
+		- Forms and controls
+			Every form help page should, at the top have a link to Standard form controls or How to use forms so user can move from any topic to how to use the basic controls etc
+			I guess in a section outlining the fields and menu options on the form there should be links to "Common menu options" and "Common controls"	 and common controls should have a link to how to use forms
+				common controls means Wiki, active, attachments, tags, names and their uniqueness etc
+		- Somewhere document that a login is good for 5 days from moment of login before needing to login again
 - Installer
 	Linux 
 		Offer as archive for docker and for bare metal