FAQ & Troubleshooting
Answers to the questions operators and administrators ask most, the exact fixes for common blockers, a glossary of the module's vocabulary, and how to escalate when you are stuck.
Troubleshooting
I can't see the Offboarding menu
Three things must all be true: the module is enabled in Settings → Manage Modules, your
role holds the base offboarding permission, and the menu cache is fresh. If you just
enabled it, clear the cache:
php erpat config:clearThe Automation and Setups items are hidden (not disabled) unless you also hold
offboarding_automation / offboarding_setups.
Starting a case says "no published template matches"
A case can only start when a published checklist template matches its separation type. Open Setups → Checklist Templates, build the template's tasks, and publish a version for that type. A brand-new template is only a draft (v0.1) until published.
Final clearance is blocked
This is by design. Open the Final clearance dialog — the server lists the exact blockers: incomplete gate tasks, unresolved assets, unverified access actions, pending required sign-offs, or open exceptions. Clear each listed item, then run clearance again.
My exception closure was rejected
Exception closure needs the offboarding_clearance permission and an approver who is
different from the case owner. If you own the case, ask another authorized user to approve the
exception — no one can wave through their own case.
Nothing releases or reminds automatically
Time-based releases (access actions becoming due) and reminders/escalations depend on the Advanced
Cron runtime being ticked and the offboarding_scheduler job being enabled. Check:
php erpat cron:list # confirm offboarding_scheduler + offboarding_reminders are registered
php erpat cron:tick # run whatever is due nowIf your server cron is not calling cron:tick, schedule it. Until then, you can still work
items manually.
A confidential case's reason is hidden from me
Confidential case reasons and pre-notification details are restricted to users with the
offboarding_confidential permission. The rest of the case (authorized actions, task
states) remains visible per your other permissions.
Why don't the external connectors call the providers?
In this version, external connectors (Microsoft Entra ID, Google Workspace, SCIM/REST, Outbound Webhooks) run in manual-verification mode — no outbound provisioning call is made. The module prompts an operator to make the change in the provider and confirm it here, and the confirmation is audited. The two internal connectors (Asset Registry, Notifications) are live.
Glossary
Getting support
OFB), the exact blocker text
from the clearance dialog, and the relevant cron output, then contact the ERPat Team. For
setup and configuration questions, start with Administration &
Setups; for step-by-step usage, see Daily Operations.