Doc chat that answers from drafts
Tools that pull from every uploaded file leak confidential drafts and stale policies.
Resources chat
Ask over the company knowledge that's been approved.
Resources chat answers questions over the company knowledge that's been approved and prepared, with citations and permission-scoped retrieval.
Evaluation focus
AI chat over employee handbook
- AI document chat for SMB
- policy chat assistant
- retrieval augmented company knowledge base
- AI knowledge base for hourly workers
- Lexical retrieval by default; vector retrieval where ready
- Citations next to every answer
- Provider keys stay server-side
Resources chat
Resources chat · Approved sources
What’s the yard opening procedure on rainy mornings?
Open with the under-canopy check first, then move equipment from bays 1–3 inside before powering up the lift.
Yard procedures v3.2 · §2Safety v1.7 · rainy ops
Generated layout — synthetic demo data.
Who it is for
- Admins enabling policy and procedure chat for employees
- Employees searching the handbook by question instead of keyword
- Ops leaders evaluating retrieval-augmented company knowledge tools
Built for these realities
The pain we hear from operators
Each pain point reflects real conversations with SMB operators evaluating workforce tools today. Yrka is shaped around these realities, not generic feature checklists.
Answers without citations
RAG tools that paraphrase without source links cannot be verified.
Provider outages that break the experience
When the provider is down or misconfigured, generic tools either crash or hallucinate.
How teams use it
Use cases we ship for today
These are the moments this surface is built around. They map to shipped product behavior and the launch scope for this area.
Employee policy chat
Employees ask questions over approved Resource pages with access-scoped retrieval.
Admin source prep
Imported drafts and stale/revoked sources are excluded until they are approved and prepared again.
Provider-aware fallbacks
Disabled or unavailable provider states fail safely; lexical retrieval remains the fallback.
Why Yrka here
What makes this different
Differentiators map to shipped product behavior. They are the reasons buyers pick this surface after comparing alternatives.
Approved sources only
Drafts, revoked sources, and unapproved content are excluded by default — not a privacy flag you have to remember to flip.
Citations + retrieval diagnostics
Every answer ships with citations and safe retrieval diagnostics so admins can verify scope.
Server-side provider keys
Provider keys stay server-side; the experience degrades gracefully when retrieval cannot be served.
How it flows
A workflow that mirrors how operators actually run the day
Three steps, three responsibilities.
- 01
Approve
Admins approve a Resource and prepare it as a source record that Resources chat is allowed to read.
- 02
Ask
Employees and admins ask questions over the sources their permissions allow them to see.
- 03
Cite
Answers ship with citations to the source pages, sections, and versions they came from.
What's inside
Resources chat highlights
Approved sources
Only prepared, approved records are eligible — drafts and revoked sources are excluded.
Access-scoped retrieval
Users see answers only from the sources their permissions allow.
Lexical and vector
Lexical default plus optional vector retrieval that falls back to lexical when needed.
Citations
Every answer cites the source page, version, and section.
Retrieval diagnostics
Clear diagnostics show why an answer came back the way it did.
Server-side keys
Provider keys never reach the client. Disabled providers return clear refusal states.
Approved sources only
Drafts, stale or revoked sources, and unprepared documents are excluded from chat until an admin approves and prepares them.
Vector retrieval with lexical fallback when embeddings are ready
Lexical retrieval is the default. Optional vector retrieval activates when prepared sources, ready embeddings, and organization AI settings are configured — and falls back cleanly when they aren't.
Scope
What's included, what's intentionally out of scope
Yrka maps every feature to its product claim so commercial conversations stay honest.
Included
- Access-scoped Resources chat
- Approved prepared source records
- Lexical retrieval by default
- Optional vector retrieval with lexical fallback when ready embeddings are enabled
- Server-side provider keys
- Safe disabled-provider states
Boundaries
- Exhaustive enterprise search
- Ungated draft-source retrieval
- Autonomous compliance determinations
Related
Where this fits in the platform
Resources
Company knowledge that asks for acknowledgement.
Publish handbook pages, organize collections, require acknowledgements, prepare approved sources, and answer questions over ready records.
ExploreAdmin assistant
An admin agent that previews everything before it acts.
A companion dock and full workspace for permission-scoped answers, contextual prompts, reviewed artifacts, dry-run previews, and confirmed writes.
ExploreTrust and security
Real controls. Honest scope. Customer in charge.
Supabase auth, organization scoping, row level security, role checks, private file storage, signed URLs, audit events, AI boundaries, and operations runbooks — described as built, not as promised.
ExploreQuestions
Common buyer questions
We surface the questions buyers actually ask — trial, support, export, mobile, payroll, provider, AI, and trust scope — in plain language.
What does Resources chat actually search?
Only approved prepared Resource records that the user has access to. Drafts, unapproved content, and revoked sources are excluded. Lexical retrieval is the default; optional vector retrieval falls back to lexical when embeddings or providers are unavailable.
How does the trial work?
Start with a 30-day card-required trial. Cancel anytime from the Stripe customer portal. Workspaces stay available for export or reactivation for 30 days after paid access ends.
Does Yrka process payroll or file taxes?
No. Yrka covers time tracking, scheduling, payroll-prep exports, and provider handoff. Customers stay in charge of payroll processing, tax filing, legal, and HR decisions.
What does mobile look like?
Responsive web and an installable PWA cover employee time entry, scheduling, resources, tasks, messages, and profile review. Employees see scoped offline read context plus queued supported writes with clear sync states.
Can we export our data?
Yes. Payroll-prep exports, schedule and time reports, and employee data exports are part of the core product. Customer data remains exportable for 30 days after paid access ends unless an earlier deletion is requested.
Ready to run the day on Yrka?
Start a 30-day trial in minutes, or book a working session to walk through the rollout with someone who has done this before.