docs/8.0/ayanova/docs/adm-users.md

@@ -94,6 +94,12 @@ Optional field designated for employee number.
 
 This is where you grant access to the different areas of AyaNova for this User. [AyaNova roles](ay-biz-admin-roles.md) are broadly defined by the business roles that User must perform so in most cases you would grant roles based on the User's actual job roles. It is better to grant less access initially and add as required.
 
+Changing a User role will take effect immediately at the server for a currently logged in User but will not fully take effect at the AyaNova web app for that user until they log out and back in again. This is because navigation options are set once upon login.
+
+This means a currently logged in user who has a role taken away will not be able to edit records of business objects not available to that role immediately upon saving their new roles in their User record as the server will return an error due to lack of rights to that object even if the local web app is still showing access to that feature.
+
+This also means when you grant a new role to a User they will need to log out and back in to see the navigation options to work with business objects available to that role.
+
 #### User type
 
 ##### Service user

docs/8.0/ayanova/docs/ay-biz-admin-migrate-v7.md

@@ -1,8 +1,4 @@
-# BUSINESS ADMINISTRATION MIGRATE TO V8
-
-#b4beta todo: go over this and clear it
-
-## OVERVIEW
+# Migrating from AyaNova 7 to AyaNova 8
 
 This page outlines the changes and setup tasks that will need to be done after migration from a business administration point of view.
 For a technical guide to migration process see the [Operations migrate guide](ops-import-v7.md)
@@ -183,9 +179,10 @@ The original status in v7 is preserved in v8 as v8 status are now a collection r
 ### View the migration log
 
 A copy of the migration log is automatically sent in AyaNova 8 in a Memo to the SuperUser account and is a mirror copy of the migration log displayed during migration.
+
 This log may contain important instructions and indications of any objects that could not be migrated or will need attention.
 
-Be sure to check this log carefully before proceeding and take any actions recommended.
+**Be sure** to check this log carefully before proceeding and take any actions recommended.
 
 ### Check your data
 
@@ -219,7 +216,7 @@ If you have any customized report templates they will need to be re-created or r
 
 The V8Migrate utility is not able to access settings in the optional add-on's RI and WBI and so is not able to automatically migrate their settings to AyaNova 8. Instead it will automatically choose safe defaults for those settings and lock out Customer access.
 
-In v7 you would make those settings within the interface provided by those optional add-on's, in AyaNova 8 all those settings can be found under Administration -> Global Settings in the "Customer Access" section and need to be set manually.
+In v7 you would make those settings within the interface provided by those optional add-on's, in AyaNova 8 all those settings can be found in the Global Settings form in the [Customer Access section](adm-global-settings.md/#customer-access-settings) and will need to be set manually.
 
 ### Enable Backup
 

docs/8.0/ayanova/docs/ay-biz-admin-roles.md

@@ -1,4 +1,58 @@
-# AUTHORIZATION ROLES
+# Authorization roles
+
+Authorization roles are used to control access to AyaNova business objects and features. Roles roughly follow typical job descriptions for various departments in a company who would use that role's features.
+
+There are a total of 17 roles available, 9 major roles and 8 'restricted' versions of most of the major roles which generally means read-only access to features and objects where the main role has full read/write access.
+
+For example a "Business administration" role can edit report templates but a "Business administration - restricted role" can only view those templates.
+
+This is useful to allow junior members of staff the ability to help other users in other departments by being able to look up information but not entrusted yet to change that information.
+
+## Roles
+
+### All roles
+
+All roles have access to their own `Home` navigation menu options in AyaNova.
+
+### SuperUser account
+
+The AyaNova super user account has all roles (except Customer roles) by default and it's roles can not be modified.
+
+### Accounting
+
+This role is intended for a person responsible for typical Accounting processes in AyaNova such as setting rates, tax codes and contracts as well as integrating AyaNova with external accounting software. There is no restricted version of this role.
+
+Accounting role can view costs and prices of any object in AyaNova.
+
+For example when an Accounting role user opens a Work order they will see prices **and** costs in addition to the other fields but a user with a `Technician` role will only see prices, not costs.
+
+The Accounting role has access to the `Accounting` navigation pane options as well as `Customers` area, most `Service` area options relevant to Accounting tasks, all `Inventory` area options and `Vendors`.
+
+### Business administration
+
+This is the most powerful role and has access to all areas of AyaNova and all objects with the sole exception of some of the more dangerous options available to the `Server operations` role. This role is appropriate for senior level administration who are interested in making changes in AyaNova including creating other Users and granting their Roles.
+
+This role has access to the `Administration` navigation pane options.
+
+This is an appropriate role for a User responsible for setting up critical settings in AyaNova that affect all users such as [Global settings](adm-global-settings.md), and various customization features which affect all users.
+
+`Business administration - restricted` this role has read-only rights to the same data as the full `Business administration` role and is more appropriate for a senior level administrator who needs to _view_ information in all areas of AyaNova but isn't involved in making changes to any data in AyaNova.
+
+### Customer
+
+This role is intended to allow access to your customers and the Customer self service support features in AyaNova such as receiving in-app notifications, requesting service etc.  If a Customer type user account is not granted the Customer role they will only have access to notification features.
+
+Customers with the Customer role are potentially able to use the Customer features of AyaNova but do not *automatically* have access to all customer features in AyaNova, those rights are finer grained and controlled in detail via the [Global settings form customer access section](adm-global-settings.md/#customer-access-settings).
+
+`Customer - restricted` role is the read-only version of the full Customer role and intended for viewing Customer centric features but not making changes like creating a new [Customer service request](svc-csr.md) for example.
+
+
+
+## How to set roles
+
+Roles are set through the [user edit form](adm-users.md#authorization-roles).
+
+00000000000000000000000000000000000
 #b4beta
 todo: overview of roles, list of roles and how they work
-NOT how to assign roles, that's in the form documentation for User or elsehwere, this is *about* roles
+NOT how to assign roles, that's in the form documentation for User or elsehwere, this is _about_ roles

docs/8.0/ayanova/docs/ay-start-changes-from-v7.md

@@ -193,7 +193,7 @@ Security groups have been replaced by a **role** based authorization system.
 In v7 you would select a security group for a user to restrict their access to objects in AyaNova.
 In v8 a user is now assigned one or more Authorization Roles which controls their access. Roles are pre-defined and pertain to the type of user for example there are roles for Inventory, Accounting, Business administration, Technician, Subcontractor etc. Whichever roles you assign to a user give them access to those areas of AyaNova.
 
-Migrating Users from AyaNova 7 will automatically set migrated Users to have no role in order to protect information security; the business administrator will need to set each user to the most appropriate new roles after migration is completed. For more about migrating from a business administration standpoint see the [business administration migration guide](ay-biz-admin-import-v7.md) and for more about the techncial aspects of the migration process see the [Migration technical guide](ops-import-v7.md).
+Migrating Users from AyaNova 7 will automatically set migrated Users to have no role in order to protect information security; the business administrator will need to set each user to the most appropriate new roles after migration is completed. For more about migrating from a business administration standpoint see the [business administration migration guide](ay-biz-admin-migrate-v7.md) and for more about the techncial aspects of the migration process see the [Migration technical guide](ops-import-v7.md).
 
 For details see the [Authorization roles](ay-biz-admin-roles.md) guide for more information.
 

docs/8.0/ayanova/docs/ops-import-v7.md

@@ -2,7 +2,7 @@
 
 This is the technical guide to the migration to v8 process.  
 
-There is also a business administration focused [guide](ay-biz-admin-import-v7.md) to migration outlining business object changes and steps that need to be taken after the migrate process has completed.
+There is also a business administration focused [guide](ay-biz-admin-migrate-v7.md) to migration outlining business object changes and steps that need to be taken after the migrate process has completed.
 
 Migration is done by the AyaNova 7 plugin "V8Migrate" which is available as an optional install from the AyaNova [Download](https://www.ayanova.com/download.htm) page.
 
@@ -97,5 +97,5 @@ We recommend you keep one or more backup copis of your AyaNova 7 database in a s
 
 * A form will popup and show the progress of the Export operation.  There is no easy way to estimate how long this will take, it depends on the network latency and speed between the Export to V8 plugin and the AyaNova 8 server as well as the number and complexity of objects entered into AyaNova and the quantity and size of files that may need to be uploaded.  Allow plenty of time for this operation.
 
-* When the migrate is finished you will be able to login to V8 and start [setting things up](ay-biz-admin-import-v7.md)
+* When the migrate is finished you will be able to login to V8 and start [setting things up](ay-biz-admin-migrate-v7.md)
 

docs/8.0/ayanova/mkdocs.yml

@@ -122,7 +122,7 @@ nav:
     - 'Authorization roles': 'ay-biz-admin-roles.md'
     - 'Select list templates': 'adm-global-select-templates.md'
     - 'Business logos': 'adm-global-logo.md'
-    - 'Importing from v7': 'ay-biz-admin-import-v7.md' 
+    - 'Migrating from v7': 'ay-biz-admin-migrate-v7.md' 
   - Trying out AyaNova:
     - 'Evaluate': 'ay-evaluate.md' 
 - Server operations guide: