Operations home
Admin Dashboard, employee Dashboard, Tasks, Imports, Reports, and notifications share the same product frame.
Yrka workforce operations
Yrka brings schedules, timecards, employee records, messages, resources, training, tasks, imports, reports, and payroll-prep handoff together without turning the product into a generic project suite or a compliance promise.
Launch posture
Core launch surface
The public entry point should route buyers toward the narrow launch product and demo review.
Current activation is a controlled card-required trial path with support-approved demo tenants for no-card or sales-led review.
Final admin dashboard and employee dashboard screenshots
Capture after Reports, onboarding, final demo data, and product asset review are complete. Use real app states only.
Admin Dashboard, employee Dashboard, Tasks, Imports, Reports, and notifications share the same product frame.
V1 reports answer operational questions without mixing provider payroll exports into everyday reporting.
Legal, trust, AI, package, and integration language maps to shipped capabilities and clear customer responsibilities.
Core launch surface
Create events, assign employees, apply rotating templates, review maker requirements, handle open-shift coverage requests, and import schedule files through review-first workflows.
Core launch surface
Employees can enter time or clock in/out based on policy. Admins review worked hours, paid non-work time, drive time, and location context when enabled.
Core launch surface
Track core employee details, documents, credentials, paystubs, company job assignments, departments, teams, job roles, profile access, employee requests, and lightweight operations-tied reviews.
Core launch surface
Keep direct messages, board announcements, app notifications, and review-required inbox work distinct but connected.
Core launch surface
Publish handbook pages, organize collections, require acknowledgements, prepare approved sources, and answer questions over ready records.
Pilot-ready surface
Create Resource-linked modules, add video links, quiz questions, passing scores, assignments, and completion review without claiming LMS compliance.
Pilot-ready surface
Coordinate work with status, priority, due dates, assignees, checklist items, comments, and activity without heavyweight project-management baggage.
Provider-gated substrate
Review external connection metadata, sync jobs, webhook ledgers, notification delivery, source readiness, and provider setup status.
Pilot-ready surface
The admin assistant works as a companion dock and full workspace for permission-scoped answers, contextual source prompts, reviewed table artifacts, dry-run previews, and confirmed writes.
Pilot-ready surface
Employee and admin Resources chat use organization AI settings and ready prepared text records with access-scoped retrieval.
Trust and readiness
Role-aware admin surfaces, organization-scoped RLS, audit events, work-item history, and integration ledgers help teams understand what changed.
Operator-assisted surface
The Theme Workbench controls factory presets, capped custom themes, brand fields, typography, shell geometry, surfaces, radii, density, and mode-specific colors.
Trust and readiness
Yrka uses Supabase auth, organization scoping, RLS, role checks, private file storage, signed URLs, audit events, and documented operations runbooks.
The launch site keeps activation, mobile, support, export, payroll-prep, provider, AI, and trust limits in plain language.
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.