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.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 |
Type |
|---|---|---|
|
Security |
Enable Single Sign On and Centralised role based management For example if the enterprises uses Entra ID, configure Entra ID for SSO and Roles/Groups Configure integration with Azure Entra ID |
Recommended |
|
Monitoring |
Enable container logging to centralised monitoring service (e.g. Splunk, Azure Monitor, Datadog) Compute Memory Storage |
Recommended for Your cloud deployment only. Not required for K SaaS |
|
Network |
Configure subdomain and certificate for internal routing |
Recommended |
|
Network |
Configure firewalls for direct connections / collectors for source integrations |
Recommended |
|
Email Integration |
Configure email service (K or internal SMTP service) for K alerts |
Optional |
|
Alerts |
Configure K and monitoring service alerts to the team supporting K |
Recommended |
|
Support |
Assign support responsibilities to a Team |
Recommended |
|
Confidentiality |
Register the product in the Enterprise Service catalog. Ensure the platform has clearly defined: Service Owner Category Classification |
Optional |
|
Upgrades |
Establish the upgrade process (automated or manual) and schedules to ensure the platform remains within the recommended support period. |
Recommended |
|
Capacity planning |
Review growth projections and use cases to ensure that the platform infrastructure is suitably sized. |
Recommended for Your cloud deployment only. Not required for K SaaS |
|
Onboarding |
Establish an onboarding process to enable Employees to request and obtain access Alternatively enable all employees to have basic read access to K |
Recommended |
|
Offboarding |
Establish a regular process to review access to K |
Recommended |
|
Documentation |
Setup documentation covering the key features, workflows, and best practices. Include FAQs to address common issues. |
Recommended |
|
Training |
Setup training material and options for key personas and use cases |
Recommended |
|
Feedback |
Establish channel to gather feedback to the accountable team (and/or vendor) |
Optional |
|
Vendor management |
Establish monthly/quarter forum with KADA aligned success manager |
Recommended |