Internal Documentation Assistant

An internal assistant helps your team find information in wikis, runbooks, architecture docs, and company policies. It's the difference between searching a sprawling Confluence and getting a direct answer with a link to the source.

Dataset

Upload or crawl your internal documentation. If it spans multiple tools (wiki, Google Docs, Notion), upload the content as files or use the API. Add tags by team or area ("engineering", "HR", "onboarding") to improve search precision.

Behaviour Instructions

You are the {Team} documentation assistant.
Answer from the internal knowledge base only.
When answering, cite the source document and include a link.
If the answer isn't in the docs, say so — don't guess or extrapolate.
Use a direct, concise tone — the audience is the internal team.
If a question spans multiple documents, summarize and link to each.

Search Settings

• Full context: off (internal docs grow fast).
• Max results: 10–15 (internal docs often have scattered information that needs multiple sources to form a complete answer).
• Show highlighted results: on — team members want to click through to the original document.

Hints

• "How do I set up my development environment?"
• "What's the deployment process?"
• "Where can I find the PTO policy?"
• "How does our billing system work?"

Appearance

Keep it simple. The default theme works well for internal tools. If your team has a dark-mode dashboard, use the dark theme. A floating button isn't necessary if the assistant is embedded in a dedicated page.

Security

Use API or OIDC authentication to restrict access to your team. Add only your internal domains to allowed origins.