The following is a sample checklist for an Enterprise deployment.
Note this excludes tasks typically managed under the onboarding program (source integration, user training and show cases etc) or sign-offs from Security, Architecture and other key stakeholder groups.
Category | Task | TypeLinks | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Security | Security | Enable Single Sign On and Centralised role based management |
| Enable container loggicFor example if the enterprises uses Entra ID, configure Entra ID for SSO and Roles/Groups |
| |||||
| 2 | Monitoring | Enable container logging to centralised monitoring service (e.g. Splunk, Azure Monitor, Datadog)
|
| ||||||||
| 3 | Alerts | Configure K and monitoring service alerts to the team supporting K |
| ||||||||
| 4 | Support | Assign support responsibilities to a Team |
| ||||||||
| 5 | Confidentiality | Register the product in the Enterprise Service catalog. Ensure the platform has clearly defined:
|
| ||||||||
| 6 | Upgrades | Establish the upgrade process (automated or manual) and schedules to ensure the platform remains within the recommended support period. |
| ||||||||
| 7 | Capacity planning | Review growth projections and use cases to ensure that the platform infrastructure is suitably sized. |
| ||||||||
| 8 | Onboarding | Establish an onboarding process to enable Employees to request and obtain access Alternatively enable all employees to have basic read access to K |
| ||||||||
| 9 | Offboarding | Establish a regular process to review access to K |
| ||||||||
| 10 | Documentation | Setup documentation covering the key features, workflows, and best practices. Include FAQs to address common issues. |
| ||||||||
| 11 | Training | Setup training material and options for key personas and use cases |
| ||||||||
| 12 | Feedback | Establish channel to gather feedback to the accountable team (and/or vendor) |
| ||||||||
| 13 | Vendor management | Establish monthly/quarter forum with KADA aligned success manager |
|