Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.yrka.io/llms.txt

Use this file to discover all available pages before exploring further.

Reports gives you a consolidated view of your organization’s operational health across every major domain in Yrka. You can filter by period, team, employee, or status, export CSV or JSON outputs from supported report cards, and save owner-confidence snapshots to record the state of your operations at a point in time. Reports is a summary and review surface — it is not a durable analytics warehouse, and it does not replace the source workflows that own each record.
Before relying on a report, complete the relevant operating workflow first. Schedule, Timekeeping, Payroll Prep, Resources, Messages, Imports, and Tasks all feed their report cards. If you run a report before those workflows are current, the numbers will not reflect your actual state.

​
Report groups

Reports are organized into groups that correspond to the major operating domains. Your access to each group depends on your admin role permissions.
Review current pay-period summaries, timecard exception counts, pending corrections, and payroll-readiness posture. The timekeeping card shows current-period totals versus the prior period where comparison is available. Payroll-readiness cards show whether the current period is on track for handoff.
Review schedule coverage gaps, underfilled events, coverage changes, and schedule health by period, location, or team. Use row actions to open the owning Schedule surface for events that need attention.
Review acknowledgement and read counts for board posts and announcements. See outstanding versus completed acknowledgement rosters for required posts.
Review training module completion rates, overdue assignments, failed attempt counts, and pass/fail distributions by module or team. Use row links to open the Training surface in Resources for follow-up.
Review active task counts, overdue tasks, blocked work, and done-but-unarchived tasks by assignee, team, or due date. Open Tasks directly from row links.
Review outstanding and completed acknowledgements for required Resource pages, with due-date posture and per-employee detail.
Review employee record, document, credential, and lifecycle event history. See active, inactive, and pending access posture across the organization.
Review import batch health, failed imports, needs-review batches, and integration data-movement summary.
Review recent sensitive activity, role changes, and security-relevant events. Available to owner and admin-management roles. See the Audit and access reports section below.
Review overall setup readiness, exception resolution state, and integration health — useful for identifying areas that need attention before a payroll close or go-live review.

​
Filtering reports

1

Open Reports

Go to Admin > Reports.
2

Check the Generated timestamp

Each report card shows when the report model was last built. Make sure the timestamp reflects recent activity before acting on the numbers.
3

Apply filters

Use the Filter reports controls to narrow by Team/group, Employee, Job, Location, Payroll period, and Schedule status where those options are available for the selected card.
4

Review warning and danger rows

Rows with warning or danger tones need attention. Warning rows need review before an operator treats the area as ready. Danger rows point to higher-risk exceptions or blocked work.
5

Open source records

Use row links to open the owning workflow — Schedule, Timekeeping, Tasks, Training, Imports — for any row that needs remediation. Do not try to resolve the issue from inside Reports.

​
Exporting reports

Export actions are available on report cards that explicitly surface an export button. Not every card has an export action — where one is absent, use the owning workflow export (Timekeeping, Payroll, Imports) instead.
Select the CSV export button on a supported card. The export filename and column set match the report card and its current filter context. Use CSV exports for spreadsheet review or handoff to other tools.
Report exports are operational summaries. Do not use them as payroll provider submission files — payroll-prep exports and provider handoff files are owned by Timekeeping and Payroll, not Reports.

​
Saving owner-confidence snapshots

After reviewing a report set, you can save a snapshot to record the current state for owner follow-up. Snapshots capture sanitized counts, warning totals, exportable-card counts, and metric summaries — they do not store row-level employee detail, provider payloads, or payroll/export files.
1

Complete your review

Work through the report cards relevant to your current review cycle. Resolve or note any warning or danger rows before saving.
2

Save the snapshot

Select Save to record the owner-confidence snapshot. This requires owner or owner-management access. The latest owner-confidence card updates after a successful save.
The Save button will be absent if your role cannot save owner-confidence snapshots. If it is missing and you expect to be able to save, confirm your role has owner or owner-management access.

​
Audit and access reports

Audit and access reports are available to admins with owner and admin-management roles. Use them for routine access posture reviews and to follow up on specific security-relevant events.

​
Reviewing audit activity

1

Find the Audit card

In Reports, locate the Audit card if your role can view it.
2

Filter the audit log

Filter by actor, event type, object type, severity, date range, or text search to focus on the events that matter. If expected rows are absent, widen the date range and clear filters before assuming the activity did not occur.
3

Open linked records

Open linked records only when the card provides a safe source link. If a row needs employee or role changes, go to Personnel or Settings — do not edit from inside Reports.

​
Reviewing access posture

1

Find the Access review card

Locate the Access review card in Reports. It shows active admin role definitions, employees with self-service enabled, and request-capable employee access grants.
2

Add owner notes and mark reviewed

Add notes in the access review card. Select Mark reviewed when no follow-up is needed — this records review evidence without assigning work.
3

Create follow-up tasks

Select Create follow-up task when someone needs to complete remediation. The task is source-linked back to the access review context and appears in Admin Tasks.
Audit and access reports support your own review. They are not SOC 2 certification, HIPAA support, a formal SLA, legal advice, or a complete forensic export.

​
Attendance reconciliation in Reports

Attendance reconciliation evidence flows from the same source as Timekeeping, Payroll Prep, and Dashboard widgets. In Reports, you can review late/no-show patterns, unscheduled work, missed clock-outs, break compliance, location context, correction history, overtime risk, and payroll-ready posture. Attendance reconciliation does not approve payroll, mutate timecards, or make employment decisions automatically. It supports planning review — follow up using Tasks or Inbox for items that need human action.

​
What Reports is not

Reports is an operational summary surface, not a durable analytics warehouse. It does not:
  • Store row-level employee detail in snapshots
  • Include precise location coordinates in default operational reports
  • Replace source workflow approvals or payroll review
  • Serve as SOC 2, HIPAA, or formal compliance attestation

​
Troubleshooting

Confirm your admin role has both the report permission and the matching source-surface permission for that card.
Align the date range, payroll period, employee, group, job, or status filters between the report and the source surface. Small differences often come from filter mismatches rather than data issues.
Use the owning workflow export instead. Not every report card has an export action — Timekeeping and Payroll own their respective export tools.
Confirm you have owner-management access and that at least one permissioned report card is visible in the current view.