Use Cases

Knowledge Base turns the answers in people's heads into pages anyone can find. Here's how two very different roles put it to work.

IT support lead at a mid-size company

You answer the same "how do I connect to the VPN?" questions every week, and you'd rather write the answer once than repeat it forever.

1. Write each fix and how-to as an Article, so the answer lives somewhere durable instead of in a one-off email.
2. Organize articles by topic so staff can self-serve the common stuff and your queue shrinks to the genuinely hard tickets.
3. Share the self-help section with a Public link so anyone can reach it without logging in, even before their account is set up.

Tip: Every time you answer the same question twice, write the article — then reply with the link next time instead of retyping.

HR operations manager at a growing company

You onboard new hires constantly and want policies and first-week steps documented once, not explained desk by desk.

1. Capture each policy and onboarding step as an Article, so "how does PTO work?" has one authoritative answer.
2. Group articles into an onboarding section a new hire can read start to finish on day one.
3. Publish it with a Public link you drop into offer letters and welcome emails, so people can read up before they even have a login.

Tip: Keep one article per policy and update it in place, so there's never a stale copy floating around in someone's inbox.