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.

Yrka enforces visibility boundaries at multiple levels so that each person sees only the data their role and access level allow. Employees see their own records through the employee app. Admins see organization-level records based on their assigned role permissions. Confidential documents stay restricted to admins with explicit document access. Understanding how these layers work together helps you configure access correctly and explain visibility boundaries to your team.

​
What employees can see

Employees access Yrka through the employee-facing app surfaces: Today, Time, Schedule, Messages, Resources, Tasks, Profile, and Clock Kiosk where enabled. The sections available to each employee depend entirely on the employee app access configuration your organization controls. Employee app access is a flag that your admins set per employee. When a section is disabled for an employee, that employee cannot see it regardless of what data exists. Within any visible section, employees see only their own records — their own time entries, their own schedule, their own messages, their own profile, and their own assigned tasks. They cannot see other employees’ data through the employee app.
Employees do not gain access to admin surfaces by having employee app access enabled. The two are entirely separate: employee app access controls self-service visibility; admin roles control organization-level access.

​
What admins can see

Admins access the organization through the admin shell surfaces: Dashboard, Schedule, Timekeeping, Messages, Resources, Personnel, Payroll, Imports, Integrations, Reports, and Settings. Which of these surfaces — and which actions within each — an admin can reach depends on their assigned role. Yrka enforces access at the route and action level. Each user sees only what their role permits — hidden tabs, blocked actions, and restricted export controls are the expected behavior for roles that lack the matching permission. This is not a display preference; it is an enforced access boundary. Some role permission areas with elevated visibility impact:
Data areaWhat it unlocks
Personnel recordsView employee profiles, records, notes, documents, credentials, and lifecycle history
Payroll exportGenerate and download pay-period handoff files
Confidential documentsView documents marked confidential in employee records
Timekeeping reviewReview time entries, exceptions, and period status
ReportsAccess organization-wide operational reporting
BillingView and manage account, plan, and payment data

​
How employee app access flags work

Employee app access flags are org-level settings that your admins manage, not personal preferences employees can change. When you enable a section for an employee, that section appears in their app. When you disable it, the section is hidden entirely. This gives your organization precise control over which self-service workflows each employee can use — without modifying their employment record or admin role. Common reasons to restrict access include:
  • Employees who are not yet onboarded to self-service workflows
  • Seasonal workers who should only see certain sections
  • Employees on leave who should not take schedule or time-entry actions
  • Terminated employees during the post-termination data transition period
Disabling employee app access does not delete the employee’s records. The data remains in Personnel and is accessible to authorized admins. If you need records removed, see the data deletion workflow in Request data export, restore, or deletion.

​
Confidential documents

Documents uploaded to an employee’s record can be marked confidential. Confidential documents are visible only to admins who have the confidential document permission enabled for their role. Employees cannot see documents marked confidential — even documents in their own record. If an employee needs access to a document, an admin with the appropriate permissions can share a non-confidential copy or a separate communication, depending on your organization’s process.
If a manager can see an employee’s record but not a specific document, check the document visibility setting. The manager may lack the confidential document permission even if they can see the employee directory.

​
Audit trail

Yrka records important changes, decisions, exports, and handoffs in an audit trail. The audit trail is available to admins with the appropriate reporting access and covers events including:
  • Role assignments and permission changes
  • Export generation (including payroll exports)
  • Access review sign-offs and follow-up task creation
  • Employee app access changes
  • Document uploads and visibility changes
  • Import commits and provider sync actions
To review the audit trail, open Reports and navigate to the audit or access-review card. Use record IDs, timestamps, and action types to find specific events. The audit trail supports operational accountability — it is evidence you can review when something needs investigation.
The audit trail supports operational review. It is not a substitute for a formal compliance certification, SOC 2 report, or legal attestation.

​
Common visibility issues

An employee can see the app but not a specific section. Check the employee app access flag for that section. The section may be disabled even if other sections are visible. An admin can see an employee’s record but not their confidential documents. Confidential document access is a separate permission from personnel access. Check the admin’s role permissions for the confidential document area specifically. An admin cannot see the Reports tab. The Reports surface requires a specific permission. An admin who can see Personnel may not automatically see Reports. Review the admin’s role configuration. A record visible to one admin is not visible to another. Both users may have access to the same surface, but their role permissions may differ at the action or data level. Compare their role configurations directly rather than assuming identical surfaces grant identical access.