diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index 41d4b31b..4742a2c5 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -17,42 +17,8 @@
 
 
 
-todo: Customer access
-	- PAUSE FOR REPORTING WHERE IT"S AT:
-		admin form has ability to set settings, backend stores them, that's about it
-		was contemplating a dialog to open for wo view with just the basic buttons available and that's it
 
-	- wo opens in popup dialog with print, wiki, attachments offered if available.
-	- 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
-	- User enter Unit on CSR or choose existing on CSR as an *OPTIONAL* available feature
-		Maybe this is also by tags, i.e. if customer tagged with "XXX" can create own units?
-		otherwise only choices are open to all or none
-	- User view wiki optional taggable IN feature
-	- User view attachments optional taggable IN feature
-	- customer views wo list when clicks on wo gets report or if not enabled can't click on wo, just see headings
-		wolist is limited set of fields to cover v7 display and maybe anything new and relevant / allowable
-	- customer wolist includes wiki and attachments if applicable
-		maybe has a dynamic template rather than using the built in templating system to drive those wiki and attachments??
-		Or does it open into a form where user can print the wo view attachments etc??
-		view signature maybe??
-
-Customer access global settings
-	view wiki, view attachments currently is contact,customer or ho with tags, should expand to also include if wo tagged
-		this way they can choose to expose only wo by wo or for all wo for contact or for ho or for customer etc
-		gives the ability to restrict to single wo's only
-		
-	Reports by tag
-		Customer "...OR WORKORDER" tagged with gives similar ability to one-off certain wo for certain reports
-			currently it's only customer tagged with and that trans key is only used here
-
-TODO: Need "Customer or Work order tagged with" trans key, use it with the reports by tag on global adn in the server rights code that checks
-todo: Need "Restrict to Work order, Contact, Customer or Head Office with any one of these tags "
-	use this with the wiki and attachments glob-settings form and server code
-
-
-Customer wo form
+TODO: Customer wo form
 	open, fetches customer version of wo data 
 	server checks what they can see and indicates in return data
 	returns:
@@ -62,8 +28,8 @@ Customer wo form
 		wo header attachments availablility
 			attachment route needs to also re-check this availability thing
 
-
-
+	when print report if allowed the *server* chooses the report template, not the client, based on the global settings
+	Look at cases re wo and csr stuff
 
 
 
diff --git a/ayanova/src/views/customer-workorder.vue b/ayanova/src/views/customer-workorder.vue
index 17230a53..5e8ac6bf 100644
--- a/ayanova/src/views/customer-workorder.vue
+++ b/ayanova/src/views/customer-workorder.vue
@@ -7,10 +7,8 @@
         <v-row>
           <h1>UNDER CONSTRUCTION</h1>
           <h2>
-            Copied from inv part assembly and not implemented as customer work
-            order yet. Backend customer rights check in conjunction with this
+            {{ $store.state.customerRights }}
           </h2>
-          {{ $store.state.customerRights }}
         </v-row>
       </v-form>
     </div>
@@ -21,11 +19,7 @@
 </template>
 
 <script>
-//THIS FORM IS CREATE ONLY
-//no delete, no duplicate, no fetch, just create or leave
-//
 const FORM_KEY = "customer-workorder";
-//const API_BASE_URL = "part-inventory/";
 
 export default {
   async created() {