Approved sources only
Imported drafts and stale/revoked sources are excluded from chat until they are approved and prepared again.
Resources chat
Ask questions over approved Resources source records.
Employee and admin Resources chat use organization AI settings and ready prepared text records with access-scoped retrieval.
Launch posture
Pilot-ready surface
Resources chat is access-scoped, lexical by default, and can use vector retrieval with lexical fallback when embeddings are ready.
Asset slot
Resources chat next to the active handbook page
Capture employee and admin Resources chat with citations after final source records are prepared.
What is ready now
These points describe shipped product behavior or explicitly scoped setup readiness. Final screenshots and recordings will be captured from the product after demo data is frozen.
Access-scoped lexical retrieval with optional vector retrieval when indexed embeddings are ready
Citations plus safe retrieval diagnostics
Provider keys stay server-side
Disabled or unavailable provider states fail safely
Pilot-ready retrieval
Lexical retrieval remains the fallback. Vector retrieval is optional and depends on prepared sources, ready embeddings, and organization AI settings.
Included scope
- 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
Not included
- Exhaustive enterprise search
- Ungated draft-source retrieval
- Autonomous compliance determinations
Asset source tracking
Product imagery is published only after the capture source, demo organization, viewport, data set, and refresh trigger are recorded.
- Route
- /agent-chat-over-docs
- Surface
- Resources chat next to the active handbook page
- Organization
- Approved demo organization after final seed reset
- Viewport
- Desktop 1440x1024 and mobile 390x844
- Data set
- Synthetic approved demo data only
- Refresh date
- Pending final product capture
- Refresh trigger
- Refresh after material UI, legal copy, seed data, data model, or route changes
Buyer FAQ
These answers keep trial, support, export, provider, AI, mobile, and trust expectations consistent across the public site.
Does Resources chat answer from every uploaded draft?
No. V1 uses access-scoped prepared Resource records. Drafts, revoked sources, and unapproved content are excluded until reviewed and prepared.
Can I start without a sales call?
The current path supports controlled trial activation. No-card demo tenants remain support-approved so capacity, provider setup, sensitive uploads, and data-retention expectations stay bounded.
What happens if we cancel?
Paid access normally ends at the end of the billing period, then the workspace enters a 30-day export/reactivation window unless a verified deletion request is completed earlier.
Does Yrka process payroll or file taxes?
No. Yrka supports timekeeping, payroll-prep exports, review, and provider handoff. Customers remain responsible for payroll processing, tax filing, legal, HR, and compliance decisions.
What mobile support is included?
Launch mobile support is responsive web/PWA-oriented. Employees get scoped offline read context and supported queued writes with visible sync states; native app-store apps and broad offline admin operation are not part of launch scope.