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.

Settings is the configuration hub for your Yrka workspace. Everything that controls how your organization operates — from how time entries are captured to how alerts are routed to your managers — lives here. Open it by selecting Settings from the admin sidebar or navigating to Admin > Settings. Each section has a clear scope label so you always know whether a change affects only your view or the entire workspace.

Settings sections

Workspace settings control your personal admin shell preferences: landing behavior, sidebar order and visibility, and the Appearance workbench handoff. Changes marked Only affects your view apply only to your signed-in session and do not change what other admins see.Use the Appearance workbench to configure your organization’s business theme, typography, brand kit, color mode, and shell density. These controls shape the product shell experience — they do not create a separate branded product or public site.
Finish your baseline employee, job, and payroll setup before treating workspace preferences as final. Personal shell preferences can always be reset if they appear stale after an update.
People and Access controls your organization’s access posture: which admin roles are available, how self-service access requests are handled, and who can approve role grants. Changes here affect the entire workspace.Per-person role edits and app access changes belong in Personnel, not Settings. Job types and record types belong in Types. Settings keeps the org-level policy; individual records stay in their owning surfaces.
Timekeeping and Payroll Prep is where you establish the rules governing how time is recorded and reviewed across your organization.Key settings include:
SettingWhat it controls
Time entry modeWhether employees clock in and out or enter time manually
Pay period anchorThe start date that defines your biweekly pay period boundaries
KioskEnable or disable the shared clock kiosk for your location
Location capture policyOff, optional, or required — controls whether employee location is recorded at clock time
Rounding and break rulesHow clock times are rounded and how breaks are classified for pay purposes
Overtime and holiday premiumThresholds and multipliers for overtime and premium pay rules
Changing the pay period anchor or time entry mode mid-cycle affects all future entries and review workflows. Confirm with your payroll process before making changes that span an open pay period.
Payroll Prep keeps a compact summary of your current vendor export settings and links to the Payroll surface for period review and export diagnostics.
Scheduling settings define your organization’s holiday calendar and schedule-readiness posture. Full schedule workflows — publishing shifts, managing open shifts, and reviewing coverage requests — remain in the Schedule surface.Use this section to configure which holidays apply to your workforce and how schedule templates handle readiness states. Import-based schedule workflows use Imports and Integrations.
Communications and Notifications controls who receives alerts when employees submit requests, corrections, or profile changes. You can route each alert type to a formal manager, department, team, job role, explicit profile, access permission, or an owner/admin fallback when no other match is found.You can also configure optional admin email notifications here — including digest cadence, quiet hours, hourly cap, and duplicate suppression. In-app notifications remain the durable source of truth; email is a supplementary channel.
Routing rule changes take effect on future alerts. They do not rewrite historical messages or work items already in Inbox.
Personal notification preferences — such as individual quiet hours or per-channel preferences — stay in the notification center in your account, not here.
Resources and Training keeps a compact quick-configuration dialog for your Resources directory posture and AI status. Full policy controls for resources, training assignments, and acknowledgements belong in the Resources surface and in AI and Agent Controls.
Imports and Integrations shows provider connection health, authorization status, and sync job readiness at a glance. Use it to confirm that a provider is active before expecting automated delivery or sync to work.OAuth and manual export setup, notification pipe configuration, and full sync history belong in the Integrations surface. Settings keeps safe readiness posture only — no provider secrets are stored or shown here.
Data, Exports, and Retention is the starting point for export tools and account data lifecycle requests. Use it before creating payroll handoffs, report exports, or submitting an account data request.For export, restore, or deletion requests, see Request data export, restore, or deletion.
Billing and Account provides a safe view of your billing status and links to the relevant account actions. Subscription changes, invoice history, payment recovery, and cancellation are handled through the Billing surface and Stripe-hosted checkout — not through Settings fields.
AI and Agent Controls lets you configure which AI provider and model your workspace uses, manage retrieval health, toggle chat features on or off, and review guardrail posture for Zavi. Provider credentials remain server-side and are never entered into customer-visible fields.See Zavi for how Zavi uses these settings to answer questions and run admin actions.

Change a setting

1

Open Settings

Navigate to Admin > Settings and select the section you want to change from the side navigation or the mobile section selector.
2

Check the scope label

Every settings panel shows a scope label — either Only affects your view or Affects this workspace. Confirm which applies before saving, especially for timekeeping, communications, and access settings that apply to your whole organization.
3

Make your change and save

Update the relevant field, toggle, or rule. Some panels save automatically; others require an explicit save action.
4

Verify in the owning workflow

Settings changes appear in their owning workflows after a refresh. For example, a communications routing change is visible in Inbox recipient behavior; a pay period anchor change is visible in the Timekeeping review table.

Common issues

Confirm that your admin role includes permission to view or edit that section. Owners and access admins control appearance, billing-adjacent, and access-sensitive settings. If the section is available but a specific control is grayed out, check both your role permission and your account status.
Refresh the owning workflow surface rather than the Settings page itself. If the change involves routing rules, allow one cycle for Inbox to reflect updated recipients. If workspace shell preferences appear stale, reset personal layout preferences and refresh.
Per-person role and app access edits belong in Personnel, not Settings. Job types and record type labels belong in Types. Settings owns org-level policy; individual records stay in their owning surfaces.