[ use case · knowledge base ]

Internal docs that document themselves.

Onboarding playbooks that are still true. Runbooks tied to the incidents they came from. Architecture decisions that live next to the code they describe. Quill brings the same drift-aware pipeline to your internal knowledge base — behind your auth, scoped to your teams.

[ what an internal page looks like ]

Familiar surface. Auth-gated content. Same drift radar.

internal.your-company.com/runbooks/billing-failover
internal · @engineering

Billing service failover runbook

1

Confirm the alert in the on-call channel.

Datadog monitor "billing-write-latency-p99" should be firing. Cross-check against the synthetic in the SRE-status channel before paging the secondary.

2

Promote the read replica.

Run ./scripts/billing/failover --to=replica-east from the bastion. Quill verified the script exists on main as of this morning.

3

Flip the read-only flag.

Set the LaunchDarkly flag billing.read_only to true. Validate with a write to the canary tenant; expect a 503.

[ three use cases that actually pay off ]

Where an internal Quill workspace earns its keep.

Onboarding playbooks

New hire reads the same setup guide your senior engineer would write today, not the one they wrote two years ago when the local dev story was completely different. The "getting started" doc actually gets you started.

Incident runbooks

Tie every runbook to the incident it came from. When the service it covers changes, the runbook lands in your team's queue with a diff. No more "the runbook says to run a script that doesn't exist anymore."

Architecture decisions

ADRs that live next to the code they describe. Quill keeps the cross-references intact when files move, so the "why we built it this way" page is still findable a year later.

[ access control ]

Behind your existing auth. Scoped per team.

Internal Quill workspaces don't ship to a public domain. They sit behind your SSO, your VPN, or both. Permissions follow your IdP groups so the right teams see the right pages — no separate user management to maintain.

SSO-gated

Enforce SAML or OIDC at the workspace edge. Configurable session lifetimes. Optional IP allowlists for sensitive workspaces. The page returns 403 to anyone outside the authorized group — no leaky redirects.

Group-scoped per page

Default-deny visibility. Each page tree opts in groups explicitly. Engineering sees runbooks; finance sees billing playbooks; everyone sees the company-wide onboarding doc. No more accidental cross-team leaks.

Search respects permissions

Internal search only returns pages the reader is permitted to open. No "title leaks" — searching can't reveal that a page exists if the searcher couldn't read it. Same model your source-code search uses.

Audit-ready

Every view, edit, and publish is logged. Streamable to your SIEM. Retention configurable up to seven years. The audit trail is the same one your security team already trusts for the rest of your stack.

[ from a platform team ]

We moved our runbooks from Notion to a Quill workspace and the number of "is this still right?" Slack messages dropped to almost zero. The drift radar pays for the seat by itself.

— SRE lead, fintech infrastructure

Give your team a knowledge base that earns its place.

Spin up an internal workspace. Point it at your repos. See what the first drift report finds — most teams discover documentation they forgot existed.