Onboarding Wizard
The getting started checklist that appears on new workspaces.
The Getting Started Checklist
When you first access your workspace, the Overview Dashboard shows a Getting Started Checklist at the top of the page. This is not a wizard in the traditional sense -- it is a live progress tracker that checks whether key setup steps have been completed.
Checklist items
The checklist tracks four milestones:
1. Upload a document
What it checks: Whether at least one ingestion job exists for your namespace.
How to complete: Go to Upload Document and upload a PDF. Planara accepts equipment manuals, service guides, parts catalogs, safety standards, and compliance documents.
Why it matters: Documents are the knowledge foundation. Without at least one ingested document, Planara has nothing to answer questions from.
2. Run an eval
What it checks: Whether at least one eval query has a last_run_at timestamp.
How to complete: Go to Eval Management, generate eval queries from your documents, approve them, and run an evaluation.
Why it matters: Evals tell you whether Planara is answering questions correctly. Running at least one eval establishes your quality baseline.
3. Invite team members
What it checks: Whether at least one user (besides yourself) is assigned to this namespace.
How to complete: Go to Team and invite a colleague via email. They will receive a magic link.
Why it matters: Planara is designed for team use. Inviting others enables feedback collection and user-level analytics.
4. Configure CKL
What it checks: Whether the Compliance Knowledge Layer is enabled for your namespace.
How to complete: Go to Safety and Compliance and enable CKL with at least one trigger term and one knowledge source.
Why it matters: CKL ensures safety warnings and compliance citations appear alongside procedure answers. For regulated industries, this is essential.
Dismissing the checklist
The checklist automatically disappears once all four items are complete. There is no manual dismiss option -- completing the steps is the only way to remove it. This is intentional: each step represents a genuine requirement for a functional deployment.