Task-centered
V1 deliberately avoids milestones, dependencies, Gantt charts, and portfolio planning.
Tasks
Coordinate work with status, priority, due dates, assignees, checklist items, comments, and activity without heavyweight project-management baggage.
Launch posture
Pilot-ready surface
Operational tasks are useful for early customers, with deliberately lightweight project-management scope.
Admin and employee Tasks surfaces
Capture admin and employee Tasks after final task examples and notification links are seeded.
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.
V1 deliberately avoids milestones, dependencies, Gantt charts, and portfolio planning.
Employees see only tasks assigned to them, and updates remain permission-scoped.
Product imagery is published only after the capture source, demo organization, viewport, data set, and refresh trigger are recorded.
These answers keep trial, support, export, provider, AI, mobile, and trust expectations consistent across the public site.
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.
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.
No. Yrka supports timekeeping, payroll-prep exports, review, and provider handoff. Customers remain responsible for payroll processing, tax filing, legal, HR, and compliance decisions.
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.
Yrka uses optional analytics on the public site to understand page interest. The authenticated app does not load GA4.