Automated Employee Onboarding & KYC Documentation Assistant
Conversational onboarding assistant guiding new hires through document submission, policy sign-off, and IT provisioning.
1. Overview & Business Value#
The Onboarding Assistant automates new hire administrative workflows, guiding incoming employees through mandatory document verification and company orientation.
1. Overview & Workflow Steps#
- Open Human Resources → Onboarding → New Hire Assistant.
- Select newly hired employee.
- The agent dispatches a personalized welcome link via email/SMS.
- The employee uploads their Kebele ID, educational credentials, and pension TIN via the mobile portal.
- The assistant performs OCR verification, populates employee master records, and requests SmartERP Sign contract execution.
{screenshot:ai-onboarding-workflow-tracker}
2. Prerequisites & Security Access Groups#
- Required Modules:
muk_ai, muk_mcp, smarterp_ai_suite - Security Group:
Ashewa AI / User(Technical ID:muk_ai.group_ai_user) - Master Data Dependencies: Configured AI provider credentials, active system prompts, and departmental cost centers.
3. Step-by-Step UI Execution & Verification#
Step 1: Navigating to the Operational Interface#
- Log into your SmartERP instance at
https://smarterp.et/odoo. - Open the main App Switcher and select Ashewa AI.
- Select the operational workspace corresponding to this agent suite.
{screenshot:62-automated-employee-onboarding-assistant-step1-navigation}
Step 2: Executing Agent Actions#
- Review agent prompts and execution parameters.
- Trigger the scheduled or on-demand workflow action.
- Validate output in the generated operational log.
{screenshot:62-automated-employee-onboarding-assistant-step2-execution}
4. Advanced Configuration Points#
- Scheduled Crons:
muk_ai.ir_cron_agent_health_checkruns every 30 minutes. - Multi-Company Isolation: Multi-company record rules ensure agent context is isolated to Company 1 (
Ashewa Technology Solutions S.C.).
5. Comprehensive Troubleshooting Matrix#
| Symptom / Error | Probable Root Cause | Resolution Action |
|---|---|---|
Agent unresponsive or timeout | Network latency or API endpoint outage. | Verify provider connection in Settings → AI Providers. |
Access Denied during agent execution | User lacks assigned operational permissions. | Assign user to the designated operational group. |
Last updated: 2026-10-30