Why is a template missing from the employee portal?
The most common reasons are:
- the template is inactive
- the template is marked internal instead of external
- the template belongs to a different company
- the employee already has a pending request for that template
Why did approval fail even though the request exists?
A request record alone is not enough. Approval checks requester-required placeholders and blocks completion if values are still missing. This is intentional so incomplete letters are not produced silently.
Why can I not add another translation for a user?
Each user is allowed only one translation per language. The UI hides already-used languages and the backend still enforces uniqueness. This keeps translation lookup deterministic.
Can I edit existing translations?
Yes. The translations relation manager supports editing existing translation rows while still preventing duplicate language records for the same user.
What happens if I change placeholder delimiters?
Existing templates may stop parsing the way you expect if they were authored with the old delimiter pair. Treat delimiter changes as a system-wide content migration concern.
What happens if I import Amharic translations before employees exist?
Those translation rows cannot attach cleanly. The importer expects the base employee to already exist and identifies the target user by id_number.
Where should I send users who want documentation?
Use /help/docs/overview as the main docs landing page.
What is the best first troubleshooting step when something feels wrong?
Identify which layer is failing: company configuration, template structure, request values, generated letter values, or print output. Most issues become much easier to solve once you isolate the layer instead of treating “the docs feature” or “the letter feature” as one big problem.