Editing Kotahi CMS overview (section)

==Implementation==
This section is a placeholder list for issues/considerations regarding implementation:
# Use of Aiga/Kotahi in parallel as teams/services are onboarded and impact on access to information and reporting needs to be considered.
# Backloading Aiga data. Kotahi does have the ability to 'import' client data, but there is no such facility for other content.
# 'Admin' users. Kotahi enables us to be self-sufficient, but only if we have suitably trained and competent people to admin our system. K'aute should identify 4-5 roles who will consistently be able to admin our system as required - including user management, and configuration of services/tasks as necessary.
# Client files. Presently, teams<ref>This issue was raised by Whanau ora team, but affects all.</ref> store client files in Sharepoint, so they can be uploaded to relevant systems when time permits. These are currently separated/identified by their Aiga client ID. If this business process needs to persist then we need to think about how client IDs will be 'migrated' and it will be possible to link Kotahi clients with Sharepoint files. Alternatively, it seems more efficient to remove this step completely and store documents directly in Kotahi. However, this requires change in operational workflow of affected teams and, as a minimum, careful backloading of all current files.