KB Article Ownership System

Add support for assigning ownership to Knowledge Base articles, similar to Confluence and other documentation platforms.

Problem

Currently, Hudu KB articles lack formal ownership, making it difficult to:

• Identify which technician maintains specific procedures

• Ensure accountability for client-specific documentation

• Know who to contact for technical questions

• Manage content when technicians leave

Proposed Solution

Phase 1: Core Ownership

Basic Functionality:

• Assign primary owner during article creation/editing (defaults to author)

• Display owner name/avatar on article pages

• Individual and bulk ownership transfer

• Filter/search articles by owner

• Owner dashboard showing owned articles

• Migration tools for existing articles

UI Changes:

• Add "Owner" dropdown in article creation/edit form

• Show owner information prominently on article display

• Link to owner's profile/contact info

Phase 2: Advanced Features

• Secondary/co-owner support

• Enhanced permissions for owners

• Notification system for ownership changes

• Approval workflows

• Client assignment integration

• Ownership analytics and reporting

Benefits for MSPs

For Technicians:

• Clear identification of subject matter experts

• Know who to contact for specific procedures

• Ownership pride improves documentation quality

For Service Managers:

• Better visibility of documentation responsibilities

• Identify knowledge gaps and training needs

• Smooth ownership transfer when staff leave

For MSPs:

• Improved client accountability

• Consistent service delivery

• Better knowledge retention

• Meet client compliance requirements

User Stories

• As a technician, I want to own procedures I create so I'm notified of changes

• As a service manager, I want to see who owns procedures for proper coverage

• As a support tech, I want to know who to contact about specific procedures

• As an MSP owner, I want to reassign ownership when technicians leave

Success Metrics

• Reduced time to identify procedure maintainers

• Increased procedure update frequency

• Improved service consistency

• Higher technician satisfaction

• Decreased duplicate procedures

MSP-Specific Considerations

• Link ownership to client assignments

• Service team alignment

• Procedure specialisation by expertise

• Clear escalation paths for complex issues

Priority: High - Addresses core MSP need for documentation governance and service delivery consistency.