Skip to content

Internal Docs

Docs is for internal technical documentation; the Knowledge Base is for user-facing help.

Appropriate content

  • Network diagrams
  • Configuration backups
  • Conditional-access documentation
  • Retention settings
  • Internal operating procedures

Create an internal article

  • Open Docs and select New Article.
  • Choose a category, enter a clear title, add the content, and apply useful tags.
  • Create the article. Without an external repository integration, it is stored with the SupportStudioK12 tenant and included in the platform’s backup process as described in the video.

Flag an outdated doc

  • At the bottom of the doc, open Out of date? Flag for revision, say briefly what has changed, and submit. The note is optional but helps whoever fixes it.
  • The doc's author is emailed with your name and note, unless you wrote the doc yourself. Admins can turn this email off under Notifications.
  • Every technician sees flagged docs under Knowledge → Docs needing revision, most-flagged first. Flagging again updates your note rather than adding a second flag.
  • The author or an admin clears the flags by saving an edit. Anyone on the team can Dismiss the flags on a doc that turns out to be accurate.
  • A draft can be flagged only by people who can open it: its author and admins.

District-owned repository integrations

Administrators can connect SharePoint through Microsoft 365 or a Google Workspace shared drive. With an integration configured, staff can author through SupportStudioK12 while the resulting content is stored in the district-owned repository. This reduces vendor lock-in and makes future platform changes easier.

Without an external integration, the video describes export in CSV or JSON rather than Word-document format.

Video 5: Docs Module — Watch on YouTube