androidlover5842/TrisolarisPMS
1
0
Fork 0
Code Issues 22 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

HR/Payroll: Worker profiles (save/edit) with minimal + full details #19

New Issue
Open
opened 2026-02-09 17:37:29 +05:30 by androidlover5842 · 0 comments
androidlover5842 commented 2026-02-09 17:37:29 +05:30
Owner
Copy Link

Goal

  • Store and maintain worker profiles so day-to-day payments, advances, and attendance are tied to a real person.

Profile levels

  • Casual (minimal):
    • name (required)
    • phone (optional but recommended for dedupe)
    • jobTitle / workType (flexible, see separate issue)
    • dailyRate (or hourlyRate)
    • payout preference (cash/UPI/bank) optional
    • active/inactive
  • Permanent (full):
    • address (optional)
    • bank/UPI details (restricted visibility)
    • salary terms (monthly) + allowances/deductions template (optional)
    • documents if needed (optional; ensure permissions)

UX

  • Create worker
  • Edit worker
  • Search workers by name/phone/job title
  • Show quick summary: last paid date, outstanding advance, active status

Security

  • Salary + bank/UPI details visible to ADMIN/MANAGER only (recommended).
  • Audit trail for edits (who changed what and when).

Engineering requirements

  • Do NOT mix system roles (permissions) with job titles.
  • Follow Room DB sync rule for edits (server -> Room -> UI).
  • Avoid duplication: shared form composable for add/edit if same fields.

Acceptance

  • Manager can create a worker once and reuse the profile for future payouts/advances/attendance.
Goal - Store and maintain worker profiles so day-to-day payments, advances, and attendance are tied to a real person. Profile levels - Casual (minimal): - name (required) - phone (optional but recommended for dedupe) - jobTitle / workType (flexible, see separate issue) - dailyRate (or hourlyRate) - payout preference (cash/UPI/bank) optional - active/inactive - Permanent (full): - address (optional) - bank/UPI details (restricted visibility) - salary terms (monthly) + allowances/deductions template (optional) - documents if needed (optional; ensure permissions) UX - Create worker - Edit worker - Search workers by name/phone/job title - Show quick summary: last paid date, outstanding advance, active status Security - Salary + bank/UPI details visible to ADMIN/MANAGER only (recommended). - Audit trail for edits (who changed what and when). Engineering requirements - Do NOT mix system roles (permissions) with job titles. - Follow Room DB sync rule for edits (server -> Room -> UI). - Avoid duplication: shared form composable for add/edit if same fields. Acceptance - Manager can create a worker once and reuse the profile for future payouts/advances/attendance.
androidlover5842 added the featureuxroom-db-synccompliancesecurityhr-payroll labels 2026-02-09 17:37:29 +05:30
androidlover5842 added this to the TrisolarisPMS Roadmap project 2026-02-09 17:37:49 +05:30
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai-ocr
AI / OCR / parsing automation
 api
API / contract / retrofit
 availability
Availability / inventory / allocation
 bug
Bug / regression
 compliance
Compliance / audit / legal requirements
 feature
User-facing functionality
 finance
Cashbook / expenses / settlements
 guest
Guest profile & identity flows
 guest-docs
Guest documents (upload/view/delete)
 hr-payroll
Staff, attendance, payroll
 integration
3rd party integrations / automation
 privacy
Privacy, consent, sensitive data handling
 room-db-sync
Must follow Room DB sync rule
 room-stay
Room stay management
 security
Security / permissions / sensitive data
 telephony
Call-related UX/integrations
 ux
User experience / UI polish
 voice-ai
Speech-to-text / voice extraction
No Label compliance feature hr-payroll room-db-sync security ux
Milestone
No items
No Milestone
Projects
Clear projects
No project TrisolarisPMS Roadmap
Assignees
Clear assignees
androidlover5842
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: androidlover5842/TrisolarisPMS#19
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?