In Humadroid, Employment Types are used to classify different forms of work relationships in your company, from full-time employees to contractors and interns. You’ll find them under:
Settings → Compliance → Employment Types
🔐 Employment Types + Required Documents: A Smart Compliance Match
Define and manage employment types with role-specific document requirements. Link critical policies directly to executive or contractor positions for better audit control.
When you create or edit an employment type, you can assign required documents to it, for example:
-
Employment contract or B2B agreement
-
Employee Code of Conduct
-
NDA (Non-Disclosure Agreement)
-
GDPR/Data Protection Policy
-
Internal Security Policy
This means every new hire assigned to that employment type will automatically be expected to review and acknowledge the right documents, and no manual steps are needed.
📂 Where Do the Documents Come From?
The documents must have been previously created and published in the Documents section of the Compliance module. Once live, they become available for selection when editing employment types.
💡 Remember: To assign documents to Employment Type, once you create a document, you need to publish it, and only then will you have this document as an option while creating or editing Employment Type.
✅ What This Enables:
-
📋 Automated onboarding – No need to remember which doc goes to whom. It’s set once by employment type.
-
🔎 Visibility – You can track who has acknowledged which documents and follow up as needed.
-
📉 Fewer errors – Admins don’t have to manually assign individual policies to each new hire, it's automatically assigned to employment types.
🔄 Updating a Document: Versioning & Notifications
When you create a new version of a document (using the “Create New Version” button), you override the old version, and once you publish the new version, it becomes a valid version.
Once published:
-
✅ All assigned users are automatically notified that a new version is available
-
✅ The previous acknowledgments are reset, users must confirm they’ve reviewed the updated content
-
✅ You get real-time visibility into who has (or hasn’t) acknowledged the new version
This ensures that no outdated procedures remain in circulation, and that compliance tracking stays up to date, especially critical for policies like security, incident response, or business continuity.
💡 Remember: a new version must be explicitly published to take effect. Only then will it replace the previous version in your policy set.
🔧 Use Case Example:
Let’s say a new developer joins on a B2B contract. You assign them the “Contractor” employment type, which already has these documents linked:
-
NDA
-
Security Policy
-
Data Handling SOP
They’ll receive only the policies relevant to their role, no irrelevant HR materials like benefit guides or paid leave policies.