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.

Resources is where you build and maintain your organization’s operational knowledge base: handbook pages, policy collections, training modules, and compliance assignments. Content you publish here becomes available to employees in their Resources tab, and pages you mark as required create acknowledgement workflows that you can track and report on. Resources also powers the knowledge chat feature in Zavi, drawing answers from approved source content you’ve reviewed and prepared.

Handbook pages and collections

Creating and publishing pages

1

Open Resources

Go to Admin > Resources.
2

Create a page

Select Create and add a title, body content, and visibility setting. You can paste prepared content directly. Save as a draft while the content is still being finalized.
3

Organize into collections

Add the page to a collection or section so employees can browse related content together. Collections work like handbook chapters — group policies by topic, department, or function.
4

Set visibility and targeting

Choose whether the page is admin-only, visible to all employees, or targeted to specific departments, teams, job roles, company jobs, or employment status. Only employee-visible pages appear in the employee Resources tab.
5

Publish

When the content is ready, publish the page. It becomes immediately visible to the targeted audience in Employee Resources after refresh.
6

Archive old pages

When a page is no longer current, archive it instead of deleting it. Archived pages leave active browsing but remain available as historical evidence.
Publishing a resource page does not create legal, HR, payroll, tax, or compliance advice from Yrka. Resources are customer-authored operating content. They are separate from the official Yrka product Manual.

Required acknowledgements

When employees must confirm they have read a page — safety policies, employee handbooks, updated procedures — mark the page as Required acknowledgement and optionally set a due date. Required acknowledgement pages:
  • Create reviewable work items in the admin Inbox as employees acknowledge
  • Appear in the Reports acknowledgement summary with outstanding and completed rosters
  • Are included in compliance evidence exports with employee, status, due date, and evidence posture
Review acknowledgement progress from Resources, Inbox, or Reports depending on the scope of your review. For a single page, the acknowledgement roster on the page itself is fastest. For a cross-team compliance overview, Reports gives you the full picture.

Training modules

Training lets you create structured learning assignments linked to your Resource pages, with quizzes, scoring, due dates, and completion tracking.

Creating a training module

1

Open Training

Go to Admin > Resources and select Training.
2

Create a module

Select Create and fill in the module title, description, and the linked Resource page or optional video URL that employees should review before taking the quiz.
3

Add quiz questions

Write questions and answer choices. Set the passing score and the maximum number of attempts allowed.
4

Set a due date and assign employees

Add a due date and assign the module to employees by selecting individuals, departments, teams, job roles, or employment status. Compliance bundles let you target multiple requirement types to the same audience in one step.
5

Publish the module

When the module is ready, publish it. Assigned employees will see it in their Resources Training section with attempt history and remaining retakes visible.
Training V1 does not claim SCORM, LMS compliance, certification issuance, or automatic discipline workflows. Admins remain responsible for reviewing training results before relying on them for employment decisions.

Reviewing results

1

Switch to Results

In Training, select the Results view to see employee-level assignment rows.
2

Filter by status or module

Filter by Status, Due, Module, Employee, or Result. Sort by score, due date, submission date, or attempt count to find the records that need attention.
3

Open a result for detail

Select a result row to review answer-level detail when you need to understand how an employee performed on specific questions.
4

Export compliance evidence

Use the Compliance panel evidence export to generate a CSV of Resource, Training, and document requirements with due dates, current status, and evidence posture. This export includes required acknowledgements even when they were not assigned through a bundle.
5

Create follow-up work

For failed, overdue, or missing results that need human follow-up, use Tasks, Inbox, or the employee profile — do not assume training completion sends every reminder automatically.

Training status meanings

StatusWhat it means
AssignedThe employee has training to complete
In progressThe employee has started but not submitted
CompleteThe employee submitted the required attempt
Passed / FailedReflects the configured passing score
WaivedThe assignment has been excused; keep the reason in the owning record
OverdueThe due date passed without completion
DraftThe module is still being authored — do not treat as employee-ready

Source readiness and knowledge chat

Yrka’s knowledge chat (available through Zavi) answers questions from your approved Resource content. Before a page can be used for chat answers, it must be reviewed and prepared as a source.

Managing sources

1

Review source records

In Resources, review the source records for pages you want to use in chat. Approve sources you have reviewed, or revoke sources for content that should not be used in chat answers.
2

Prepare sources for retrieval

After approval, prepare or re-prepare stale source records so they are indexed and ready for retrieval. If a source record shows as stale, re-prepare it before relying on chat to answer from it.
3

Configure AI retrieval settings

Go to Settings > AI and Agent Controls to set the retrieval mode (lexical or vector-with-lexical-fallback), choose the AI provider and model, and toggle chat on or off. Provider secrets stay server-side — do not enter them in customer-visible fields.
The official Yrka Manual (which Zavi uses for product guidance) is separate from your customer-authored Resources content. Chat answers from Resources draw only from your organization’s approved, prepared pages — not from Yrka’s own documentation.

Directory settings

Resources includes a quick configuration dialog for directory visibility — controlling which organization chart and directory details appear to employees. For full directory and AI posture controls, go to Settings > Resources and Training and Settings > AI and Agent Controls.

Troubleshooting

Check that the page is published (not saved as draft or archived), that its visibility is set to employee-visible, that any targeting (department, team, job role) includes the employee, and that the employee has app access enabled.
Check that the source record is approved, in a prepared/indexed state, and that the retrieval mode and AI provider are configured in Settings > AI and Agent Controls.
Check assignment targeting, confirm the employee belongs to the targeted canonical department, team, or job role, and verify they have employee app access.
Open the question answer key and review the employee’s latest attempt detail to confirm the correct answers are configured.
The compliance export includes required resource acknowledgements even outside formal bundles. If entries are missing, confirm the page is marked required and targeted to active employees.