Employer integrations should belong to the organization, not only to the platform admin. That is why Helmroot supports organization-scoped configuration for branded email, team chat, workspace suite, and productivity suite so each employer can communicate with employees using its own company context.
Email configuration that employees can trust
- Brand name and company logo for employee-facing messages
- Portal URL so employees go to the correct workspace
- Support email, support phone, and reply-to email for real follow-up
- SMTP host, port, secure mode, username, and secret with masking on read
- Test email actions so HR can verify delivery before rollout
team chat, workspace suite, and productivity suite coverage
- team chat webhook and channel configuration for HR, workflow, and operational notifications
- workspace suite auth URL and configuration fields for calendar, email, and identity workflows
- productivity suite auth URL and configuration fields for Outlook, Teams, calendar, and identity workflows
- Preserved secrets when a submitted field is blank or still masked
- Role restrictions so only allowed employer roles can update organization integrations
Who should have access
A practical HRMS needs employer-side control. Business owners, organization admins, and HR admins should be able to maintain employer integrations, while global platform admin settings remain separate.
- Business owner: final owner for the organization workspace and integration setup
- Organization admin: operational admin who can maintain company settings
- HR admin: HR-side admin who can configure communication used by employee lifecycle workflows
- Employee: receives branded communication and self-service access, but should not manage secrets
- Client or external user: receives only the client-facing communication needed for that workflow
Operational rollout checklist
- Save email branding first: company name, logo, portal URL, support contact, and reply-to address
- Send a test email to HR and verify logo, sender, reply-to, and links
- Connect team chat and send a test message to the configured channel
- Prepare workspace suite and productivity suite OAuth settings before enabling calendar or identity workflows
- Review role access so HR admins can work without exposing global platform controls
FAQ
Can HR manage email settings?
Yes. Employer-side integration writes should be available to business owners, organization admins, and HR admins.
Are secrets visible after saving?
No. Secrets should be masked on read and preserved when blank or masked values are submitted.
Can every organization use a different logo?
Yes. Email branding is organization-scoped so each employer can send employee communication using its own logo and support context.
Why add team chat and calendar integrations to HRMS?
People operations depend on timely reminders, approvals, interviews, attendance, payroll, and manager follow-up. team chat, workspace suite, and productivity suite make those workflows more useful.