Getting started with Polp
Set up your workspace, connect knowledge, and help your team ask source-backed questions from day one.
The fastest way to activate Polp is to start with a small set of useful documents, test real questions, and expand from there.
This guide orders the first actions so the assistant has useful context and the team knows how to use it.
Quick checklist
- Connect a knowledge source or upload key documents.
- Ask a real question and review the cited sources.
- Invite the people who answer repeated internal questions today.
- Review permissions if content differs by team, role, or department.
- Use knowledge quality to detect gaps.
1. Start with the knowledge people ask for most
You do not need to connect the whole company on day one. Start with documents that answer repeated questions: internal policies, procedures, pricing, contract templates, onboarding manuals, or sales documentation.
If your team already uses Google Drive, connect one controlled folder first. If content is scattered, upload a small reviewed document pack.
- Prioritize current, clearly named documents.
- Avoid old duplicates that contradict current information.
- Separate sensitive documents before inviting the whole team.
2. Validate one real question
Before inviting more people, test a question someone would actually ask during work. A good first test includes context: team, customer, policy, or process.
Check whether the answer cites sources and whether those sources are correct. If Polp cannot answer, the knowledge base usually lacks the right document or the question needs more context.
- Ask: "According to our policy, how do I request vacation?"
- Ask: "What should sales do before sending a proposal?"
- Ask: "What conditions are documented for customer X?"
3. Invite the right team
Start with people who receive or ask repeated internal questions. Their early use reveals missing documents and processes that need better structure.
In a company account, administrators can invite members and decide who can manage knowledge, team access, or permissions.
4. Set permissions before scaling
If documents differ by department, customer, or function, configure document types and roles before opening access to the whole organization.
Permissions help each person query only the information they should see.
5. Improve with unanswered questions
The first weeks are ideal for reviewing knowledge gaps. If an answer has low confidence, no sources, or negative feedback, turn that signal into a documentation improvement.
Apply this guide in your workspace
Open Polp to connect sources, upload documents, or test a real question with your company's sources.
Go to Polp