Trust & Intellectual Property
Teach operators. Protect the platform.
A foundational design principle of Kinship University is the protection of Kinship's intellectual property. KinU teaches customers how to successfully use and administer Kinship — not how to recreate or engineer the underlying software.
- Business processes & end-user workflows
- Finance, payments, and vendor management
- Case management & supervisor workflows
- Reporting and analytics
- User administration & security configuration (approved features only)
- Release and change readiness
- Implementation best practices
- Customer support procedures
- Data quality, testing, and change management
- Source code or proprietary algorithms
- Internal development documentation
- Product architecture intended for engineering
- Deployment pipelines & release tooling
- Development repositories
- Internal engineering tools
- Trade secrets
- Confidential technical documentation
- Internal software design details
Application administration is treated as a separate discipline from software engineering.
Content classification system
Every piece of KinU content carries a classification and audience. Users only see content appropriate to their assigned permissions.
| Classification | Audience | Example content |
|---|---|---|
Public | Anyone | Marketing overviews, course descriptions, published learning paths. |
Customer Training | Authenticated customers | Standard courses, lessons, and assessments for using Kinship. |
Certified Administrator | Certified admins only | Deep-dive administration training, security configuration, incident response. |
Organization Administrator | Org admins in a locality | Assignment templates, readiness reports, workforce oversight material. |
Internal Operations | Kinship Systems staff | Customer success, implementation, and support-operations playbooks. |
Confidential | Approved personnel only | Sensitive operational or contractual material — never customer-facing. |
Internal Engineering | Authorized engineering staff | Never published to KinU. Governed by separate IP and security agreements. |
DeliveryProof → Approval → Publication
Not every document in DeliveryProof becomes training content. Every candidate asset passes through a documented approval workflow before it can reach a learner.
- 1 Step 1
Sourced
Identified in DeliveryProof
- 2 Step 2
Classified
Audience & sensitivity applied
- 3 Step 3
Reviewed
SME + editorial review
- 4 Step 4
Approved
Publication approval on record
- 5 Step 5
Published
Delivered inside KinU with audience scope
This page describes the design principles that guide Kinship University. It is maintained by Kinship Systems and does not constitute a certification, audit, or legal commitment.