---
title: "Internal Knowledge Base: Manage SOPs and Standards"
sidebarTitle: "Introduction"
description: "A hub for your organization's SOPs, how-to guides, and company standards — built for teams who need governed, versioned, and auditable content."
---

> **For AI agents:** the complete documentation index is at [llms.txt](/llms.txt). Append `.md` to any page URL for its markdown version.

The Internal Knowledge Base gives your organization one authoritative place to create, maintain, and govern the operational content your teams depend on every day. Whether you're an operations manager standardizing a critical process, a team lead onboarding new hires, or a department head enforcing company-wide standards, the Internal KB ensures everyone works from the same approved, up-to-date source of truth — not a scattered collection of stale documents and outdated wikis.

## What the Internal KB Is

The Internal KB is a **structured, governed content repository** for the three core document types that keep organizations running consistently:

- **Standard Operating Procedures (SOPs):** Step-by-step instructions for repeatable business processes — from employee onboarding to incident response to vendor management.
- **How-To Guides:** Task-focused references that help team members accomplish specific goals quickly, without needing to read an entire process document.
- **Company Standards:** Authoritative definitions of your organization's expectations — writing style, design guidelines, security policies, code conventions, and beyond.

Every piece of content in the Internal KB lives inside a defined structure, carries a version history, and moves through a configurable approval workflow before it reaches your team.

## Who Uses the Internal KB

The Internal KB is built for everyone in your organization who creates, approves, or consumes operational content:

| Role | Primary Use |
|---|---|
| **Operations Teams** | Author and maintain SOPs for cross-functional processes |
| **Managers & Team Leads** | Review and approve content before it goes live; monitor version changes |
| **New Hires** | Find onboarding materials, policies, and process guides in one place |
| **Individual Contributors** | Look up the right way to complete a task without interrupting colleagues |
| **HR & Compliance** | Publish and enforce company-wide policy standards with audit trails |

## Key Capabilities

### Structured SOP Templates

Start every new SOP from a validated template rather than a blank page. Templates enforce consistent structure — purpose, scope, roles and responsibilities, step-by-step procedure, and revision history — so every document meets your organization's standards from the first draft.

### Guide Authoring with a Rich Editor

Write how-to guides using a rich editing environment that supports callouts, code blocks, embedded media, and reusable content snippets. Format content for clarity without fighting your tooling.

### Content Governance and Approval Workflows

Define multi-stage review workflows for any content type. Route new SOPs through a subject-matter expert, a manager, and a compliance reviewer before publishing — all tracked automatically. No document goes live without the right sign-offs.

### Version Control and Change History

Every save creates a version. Compare any two versions side by side, restore a previous draft, and see exactly who changed what and when. Audit trails are automatically maintained for compliance-sensitive content.

### Role-Based Permissions

Control who can view, edit, comment on, or approve each document or collection. Assign permissions at the workspace, folder, or individual document level to match your organization's access model.

## How the Internal KB Differs from a Wiki

Most teams reach for a wiki when they need to document processes, and wikis work well for informal, collaborative notes. The Internal KB is designed for something different: **content that must be accurate, approved, and auditable.**

<Info>
A wiki lets anyone edit anything at any time — great for brainstorming and informal documentation. The Internal KB enforces structured templates, mandatory review cycles, and version-locked approvals, so the content your team relies on for critical processes is always trustworthy and traceable.
</Info>

The key distinctions at a glance:

- **Structure:** Every document follows a defined template for its content type. Free-form writing is still possible, but the structure is there when you need it.
- **Governance:** Content moves through approval stages before publishing. Edits to live documents trigger a new review cycle.
- **Accountability:** Every change is attributed to a named author and timestamped. Approvals are logged with the reviewer's identity and date.
- **Formal Review Cycles:** You set a review cadence for each document — quarterly, annually, or triggered by a specific event — and the system reminds owners when content is due for revalidation.

## Explore the Internal KB

<Columns cols={2}>
  <Card
    title="SOPs Overview"
    icon="list-check"
    href="/internal/sops/overview"
  >
    Learn how Standard Operating Procedures are structured, authored, and governed in the Internal KB.
  </Card>
  <Card
    title="How-To Guides Overview"
    icon="book-open"
    href="/internal/how-to/overview"
  >
    Discover how to create task-focused guides that help team members get things done quickly and correctly.
  </Card>
  <Card
    title="Company Standards"
    icon="shield-check"
    href="/internal/standards/overview"
  >
    Explore how to publish and enforce organization-wide standards for writing, design, security, and more.
  </Card>
  <Card
    title="Getting Started"
    icon="rocket"
    href="/internal/getting-started"
  >
    Set up your workspace, learn the content structure, and create your first document in under 15 minutes.
  </Card>
</Columns>