> ## 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 glossary of terms and concepts > Definitions for terms and concepts you'll encounter across the Yrka app, Manual, and Zavi answers — covering roles, surfaces, workflows, and more. Use this glossary when a Yrka term appears in the app, in a Manual article, or in a Zavi answer and you want to understand its customer-facing meaning. Terms here define what something is; for step-by-step instructions, follow the linked article or open the related surface in the app. Some terms describe admin-only surfaces — employees may not see the corresponding section depending on the app access your organization has enabled. An owner or operator review of admin roles, employee app access, and request-capable grants — completed before launch or on a recurring operational cadence. Access reviews are a customer-controlled workflow; Yrka surfaces current state and records sign-off, but the access decisions belong to your organization. A user with organization-level access to one or more admin surfaces. Admins still see only the surfaces and actions their role permissions allow — having an admin account does not mean having every permission. The grouped admin area for operational setup surfaces including Workflows, Integrations, Imports, Types, and Payroll. Admin Tools surfaces require the matching role permissions to access. A Zavi-assisted action that uses an allowlisted Yrka route action. Actions that make meaningful changes are shown as previews for your confirmation before they execute, unless an explicitly guarded path is configured. A board post intended for a defined audience. Announcements can require acknowledgement from recipients when the posting workflow supports it. The admin surface for approved business theme and brand controls. Appearance settings change how the app looks for your organization; they do not affect permissions or billing state. A non-destructive way to remove an old item from the active queue while keeping its history available. Archiving is reversible; it does not delete the record. A link between a piece of work and a person, department, team, company job, job role, or access role. Examples include a schedule shift assigned to an employee, a task assigned to a team, or a training module assigned to a department. The reviewable record of important changes, decisions, exports, and handoffs in your organization. Audit trails support operational accountability — they are not a compliance certification on their own. A shared message channel used for posts, acknowledgements, reactions, threads, and operational announcements. Boards are accessible from the Messages surface. The authenticated `/clock` surface used for clock-code time entry when your organization uses shared-device kiosk clocking. The clock kiosk requires authentication and is organization-scoped. A reviewed timekeeping flow for fixing or explaining a time entry after normal editing is unavailable or manager review is required. Correction requests go through a review workflow before they change the timecard record. A schedule workflow where an employee asks for help covering an assigned shift, or where an employee offers help through an open-shift or marketplace path. The admin command board showing current operational signals, required actions, widgets, quick actions, setup health indicators, and drilldowns into key workflows. A temporary condition where a provider, network, queue, or app feature needs retry, fallback, or support review before normal operation resumes. See [Troubleshoot common Yrka issues](/reference/troubleshooting) for how to handle degraded states. A durable organization structure record for a stable business function or operating area. Departments are used for assignments, reporting, and filtering — they do not grant app permissions. The organization-controlled access setting that determines which self-service sections are visible to an employee in the employee-facing app. Employee app access is set by admins per employee and is separate from admin role permissions. A customer-safe record or status that helps an operator understand what happened — for example, import warnings, export manifests, source links, sync history, or audit events. Evidence supports review; it is not a formal compliance record. A reviewed handoff file or report output generated by Yrka. An export does not mean Yrka has submitted data to a payroll, tax, or HR provider — it means a file has been prepared for your review and handoff. A review-first file or provider intake flow that stages rows for mapping, validation, review, and commit. Imports do not change live data until an authorized admin commits the reviewed result. A connection, provider profile, webhook, sync, or reviewed handoff path between Yrka and another system. Integrations are bounded by the provider state shown in the app; Yrka does not guarantee external provider availability or delivery. A normalized position or job-function record describing what a person does in the organization. Job roles are separate from app access roles and company jobs — they describe work function, not system permissions. The official Yrka-authored help content surfaced in the app and in the documentation site. Manual content is maintained by Yrka and is separate from customer-authored Resources. A source path shown alongside a Zavi Manual answer so you can verify where the answer came from and read the full article. The schedule area for open shifts, coverage offers, and coverage-request review, where enabled by your organization. The highest-trust customer role in Yrka, carrying every active permission. Owners handle account management, billing, access reviews, launch decisions, and sensitive operational actions. Assign the Owner role only to people who hold full account accountability. The Yrka workflow for reviewing timecards, pay-period status, export readiness, snapshots, and handoff files before final payroll work happens outside Yrka. Payroll prep produces an export file; it does not submit payroll to a provider. The admin surface for the employee directory, profiles, records, documents, credentials, company jobs, departments, teams, job roles, reporting, access, lifecycle, notes, and reviews. Personnel is the central admin surface for employee data management. The employee self-service route for employee-visible details, documents, credentials, schedule context, timecard and payroll context, and shared reviews where enabled. Employees access Profile from the employee app. An external system connected to Yrka, such as a payroll processor, calendar, storage service, email system, messaging platform, SMS gateway, or identity provider. Provider availability and behavior are outside Yrka's control. A reviewed action that makes prepared content visible to the intended audience — for example, publishing a schedule, a Resource page, or a board post. Publishing is a deliberate step separate from creating or drafting content. Customer-authored handbook, training, directory, or knowledge content managed in the Resources surface. Resources are not the official Yrka Manual; they are content your organization creates and maintains. A product boundary where data is staged, previewed, mapped, or checked before an operator commits, publishes, exports, or confirms the action. Review-first workflows apply to imports, payroll exports, provider syncs, and certain schedule and resource actions. A URL or app entry point such as the admin schedule tab, the employee profile, or the clock kiosk. Routes are the navigable destinations within the Yrka app. A saved review point — often used for owner confidence or payroll-prep review — that preserves sanitized status and summary context at a point in time. A visible area of the Yrka app, such as Dashboard, Schedule, Timekeeping, Messages, Resources, Profile, or Clock Kiosk. Surfaces are what you navigate to in the app to complete a workflow. A bounded data refresh or provider movement workflow. Sync history shows state, errors, retry posture, and source links where supported. A sync completing in Yrka does not guarantee the external provider has accepted or processed the data. An assignable operational follow-up item with status, assignees, comments, due context, and employee visibility when assigned to an employee. Tasks are used to track required actions and follow-ups. A flexible operational grouping for coordination, scheduling, messages, Resources, Training, reports, and review context. Teams do not define the formal company hierarchy and do not grant app permissions. The employee-facing flow for clocking in and out or manually entering work time. Time entries feed into the timekeeping review workflow. The admin-facing review surface for timecards, pay periods, corrections, evidence, exceptions, and exports. Timekeeping is where admins and payroll managers review and finalize time data before payroll prep. The admin taxonomy surface for job types, employee record types, and role labels that affect other workflows. Changes to Types can affect how records are categorized and filtered across the app. A review queue item, often created by imports, requests, acknowledgements, messages, or operational exceptions. Work items appear in the relevant admin surface and require a review action to resolve. A repeatable operational loop in Yrka: start from a surface, review the required context, take the supported action, verify the result, and follow up through the owning surface. The Yrka assistant for Manual answers, permission-scoped admin help, reviewed action previews, artifacts, citations, feedback, and desktop Spotlight handoff. Zavi can explain workflows and surface relevant Manual articles; it does not take actions without your confirmation for meaningful writes.