Operational knowledge
Resources are built for policies, procedures, directories, and reference material employees need during the workday.
Resources
Company knowledge with acknowledgements and source boundaries.
Publish handbook pages, organize collections, require acknowledgements, prepare approved sources, and answer questions over ready records.
Launch posture
Core launch surface
Published Resources, collections, acknowledgements, and source approval are core launch surfaces.
Asset slot
Admin Resources and employee handbook/chat split view
Capture handbook, directory, source readiness, and employee chat states after final content is approved.
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.
Published employee Resources and admin-only content boundaries
Required acknowledgements tied to page versions
Compliance bundles can target company jobs, departments, teams, job roles, explicit employees, and employment status
Prepared source records for Resources chat, with optional vector retrieval and lexical fallback when embeddings are ready
Source readiness
Imported or edited content is not chat-ready until an admin approves and prepares the source.
Included scope
- Published Resources
- Collections
- Acknowledgements
- Source approval
- Prepared text records
- Reviewed Notion and Google Drive source export staging
- Live Google Drive, SharePoint/OneDrive, and Notion source staging with Resources review
- Company job, department, team, job-role, explicit employee, and employment-status compliance bundle targeting where configured
Not included
- Guaranteed legal policy correctness
- Unapproved source chat
- Compliance knowledge base claim
Asset source tracking
Product imagery is published only after the capture source, demo organization, viewport, data set, and refresh trigger are recorded.
- Route
- /resources
- Surface
- Admin Resources and employee handbook/chat split view
- 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.
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.