admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2022-06-22 20:22:10 +00:00
parent 135ff75948
commit 994f60637c
2 changed files with 27 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
devdocs/todo.txt
View File

@@ -13,6 +13,30 @@ DOING: adding integration objects and routes for qbi and others
needs to be available to bizadmin I guess and possibly accounting?? or should each integration control which roles see it??
or should the UI for each integration be *in* the integration itself and also in one place for biz admin to super control all integrations and troubleshoot log sb available to ops
todo: doc front end additions for integrations
in docs the role rights to integration object is:
Change = AuthorizationRoles.BizAdmin
| AuthorizationRoles.Service
| AuthorizationRoles.Inventory
| AuthorizationRoles.Accounting
| AuthorizationRoles.Tech
| AuthorizationRoles.Sales
| AuthorizationRoles.OpsAdmin,
ReadFullRecord = AuthorizationRoles.BizAdmin
| AuthorizationRoles.Service
| AuthorizationRoles.Inventory
| AuthorizationRoles.Accounting
| AuthorizationRoles.Tech
| AuthorizationRoles.Sales
| AuthorizationRoles.OpsAdmin,
Select = AuthorizationRoles.BizAdmin
| AuthorizationRoles.Service
| AuthorizationRoles.Inventory
| AuthorizationRoles.Accounting
| AuthorizationRoles.Tech
| AuthorizationRoles.Sales
| AuthorizationRoles.OpsAdmin,
However, the UI at client likely only shows for a biz admin role so these are actually two separate things to document unlike normally when the ayaclient is the only thing to document
JUST DONE: posted rc.1 updated forum (and turned off "views" column in custom css in forum as well it was looking pathetic)

6
server/AyaNova/biz/BizRoles.cs
View File

File diff suppressed because one or more lines are too long