Understand HRM v1.3.0 tenant scope
Understand how install and migration code applies schema changes to the current SaaS tenant while preserving other tenants.
Exact navigation Admin Area → Setup → Modules → Human Resource Management
Code-backed scope These instructions follow Human Resource Management v1.3.0. Use only controls visible to your permission level and confirm the saved record or audit entry after every action.
What you need before you start
- Access to Admin Area → Setup → Modules → Human Resource Management.
- The Human Resource Management: View capability or administrator access.
- The correct employee, record, period or authorised evidence.
How to do it
- Open the module from the tenant admin area that requires the upgrade.
- Run the upgrade from that tenant context.
- Verify the current tenant’s HRM tables and pages.
- Repeat separately only for another tenant that requires the same module upgrade.
What the module checks
- The installer uses db_prefix() from the active tenant connection.
- Migrations 120 and 130 call the module installer for the current connection.
- No cross-tenant database loop is implemented in these migration classes.
What happens next
The module saves the permitted change and records the resulting status, version, delivery or synchronisation evidence. Reopen the relevant register and verify it.
Troubleshooting
- If the control is missing, confirm the required HRM permission and module version 1.3.0.
- If saving fails, correct the exact field or state named in the validation message.
- If an email/automation is missing, review the module delivery/audit log and host cron/mail settings.
HR data safety Restrict identity, right-to-work, payroll, bank, health, disciplinary and document information to authorised staff. Do not place protected values in free-text notes, email recipients or screenshots.
Browse connected topics: human resource management version 1 3 0