KKnowledge Hub
Submit Doc Request

Admin dashboard

Knowledge base at a glance.

Monitor documentation health, take action on gaps, and keep the knowledge base moving.

Total articles
59
Published
56
Needs review
2
Drafts
3

Section 1

Documentation analytics

What is happening across the knowledge base right now.

Documentation health

Breakdown of all KB articles.

  • Published56
  • Needs review2
  • Drafts3
Most viewed articles

Top performing articles in the last 30 days.

Recent activity
  • Forgot your password
    Updated 2026-06-25
    Published
  • Reset multi-factor authentication
    Updated 2026-06-24
    Published
  • Unlock your account
    Updated 2026-06-20
    Published
  • Google Workspace login
    Updated 2026-06-10
    Published
  • Single sign-on problems
    Updated 2026-06-19
    Published
Searches without results

Gaps in the knowledge base to prioritize next.

  • okta push not arriving14 searches
  • external monitor flickering9 searches
  • zoom background greyed out7 searches
  • figma sso error5 searches
  • airpods not switching devices4 searches

Section 1.5 · Live

Documentation requests

Requests submitted through the form, pulled live from the Documentation_Requests sheet.

Submitted requests

Live from Google Apps Script · Documentation_Requests sheet.

Section 2

Quick actions

Jump straight into the most common admin tasks.

Preview imported article
See how a Google Sheets / Docs / CSV import renders before publishing.
Open preview

Section 2.5 · Phase 2 preview

Knowledge capture

Capture organizational knowledge from manual submissions, business documents, and connected systems. Imported content is prepared as draft documentation before entering the review and publishing workflow.

Capture sources

Bring in existing documents

Connected systems

Sync from tools your team already uses

AI processing

Transform raw content into polished knowledge

Section 3

Documentation workflow

How a request becomes a published article.

  1. Step 1
    Issue Discovered
  2. Step 2
    Request Submitted
  3. Step 3
    Admin Review
  4. Step 4
    Article Created
  5. Step 5
    Technical Review
  6. Step 6
    Published
  7. Step 7
    Employees Search KB
  8. Step 8
    Feedback Collected
  9. Step 9
    Continuous Improvement

Section 3.5 · MVP Concept Demo

Automation workflow demo

A visual preview of the production automation using Google Workspace, Make.com, and Slack.

MVP Concept DemoVisual only · No real APIs connected

Automation workflow demo

This demo shows how documentation requests could move from submission to review, approval, and publishing using Google Workspace, Slack, and workflow automation.

This prototype does not connect to private company tools. It demonstrates the intended automation workflow for production.
Workflow
  1. Step 1
    Employee submits request
    Pending
  2. Step 2
    Saved to Google Sheets
    Pending
  3. Step 3
    Make.com watches for new rows
    Pending
  4. Step 4
    Slack alert sent to IT / Admin
    Pending
  5. Step 5
    Admin reviews request
    Pending
  6. Step 6
    Article drafted
    Pending
  7. Step 7
    Manager approves
    Pending
  8. Step 8
    Published to IT Support Hub
    Pending
  9. Step 9
    Future employees find the answer
    Pending
documentation-requests · Google Sheets
Request IDTitleCategoryPriorityStatusSubmittedOwner
REQ-1039Slack login loop after SSO resetApplicationsHighPublished2026-06-24M. Chen
REQ-1040Zoom camera missing on macOS 15HardwareMediumIn Review2026-06-27R. Patel
REQ-1041Printer showing offline in FinderHardwareLowDrafted2026-06-30S. Alvarez
#it-requests· Slack
Slack alert will appear when the workflow runs.
Make.com scenario
Google Sheets → Slack → Task creation
Idle
Trigger
New Sheets row
Action
Notify Slack channel
Action
Update status + assign owner
Action
Create draft doc task

Section 4

Documentation best practices

Standards to keep every article useful and trustworthy.

Guidelines

Write once, help forever.

  • Write clear, descriptive titles.
  • Keep steps short and scannable.
  • Use screenshots wherever possible.
  • Review documentation quarterly.
  • Archive outdated articles promptly.
  • Always verify technical accuracy.