From f9fa83a9a9f1b5d7609ffaabdb224375440d2e6e Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Fri, 3 Jan 2020 00:03:38 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 9301e385..5a495315 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -47,7 +47,13 @@ CURRENT TODOs SHELL / NAV / MENUS / LAYOUT - +TODO: Pin down all roles and rights see core-roles.txt in server project + - Currently trying to see if I need a sales role and 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 TODO: Enforce role rights for menu items once it's stubbed out