7. Workflows: module-wise & app-wise

Generated from the fact-only workflows chapter (123 workflows). Apps are taken from the Help Center pages each workflow cites. Web columns: SA Super Admin · A Admin · M Managers · E Employee · E-CRM Employee Sales CRM web · I LMS Instructor. Mobile columns: HCM, Lite, CRM, Claims. A dot means a cited page documents that workflow on that app.

Part 1: App-wise matrix

ID	Workflow	SA	A	M	E	E-CRM	I	HCM	Lite	CRM	Claims
A1	Login (web, Employee / Super Admin)	●		●	●			●		●
A2	Users Login creation (Admin creates credentials)		●	●
A3	Employee Password Reset (Admin)		●
A4	Change Password (Employee)		●		●
A5	Employee profile edit and picture upload		●		●
A6	Employee onboarding checklist view			●	●
B1	New hire to first login (end-to-end)		●	●
B2	Employee Directory maintenance			●
B3	Document approval			●
B4	Onboarding checklist assignment		●	●
B5	Onboarding checklist completion and No Due			●
B6	Induction program (HR manager)		●	●
B7	Employee Reports			●
B8	Excel upload of employees			●
B9	Employee Department and Designation mapping		●
C1	Biometric ID mapping		●
C2	Attendance request by employee (three entry points)				●			●
C3	Attendance request on behalf of employee (Manager)			●
C4	Attendance request approval (three ways)			●				●
C5	Shift change request (employee) and approval with swap (manager)			●	●
C6	Permission request (employee) and approval (manager)		●	●	●
C7	Attendance regularization (employee)		●		●
C8	Manager attendance regularization and approval			●
C9	Shift creation and assignment (Admin, Manager)		●	●
C10	Week-off configuration		●	●
C11	Shift rotation: create sequence, assign, reassign			●
C12	Excel upload of attendance (Manager)			●
C13	Face capture and enrolment (mobile HCM and Lite)							●	●
C14	Receptionist (front office) check-in and check-out							●	●
C15	Geo-location (branch location) configuration		●					●
C16	Extra Days Slab configuration and penalty designations (Admin)		●
C17	Extra Days and Penalty Days reports			●	●
C18	Missed Punch report and default punch-out		●	●	●
C19	Attendance report retrieval (Super Admin, Admin, Manager, Employee)	●	●	●	●
C20	Attendance Messages Master (Admin)		●
C21	Shift wise report			●
D1	Leave policy activation (default leaves)		●
D2	Leave policy deactivation		●
D3	Common leave rules configuration		●
D4	Leave type configuration (per type) and Advanced leave		●
D5	Leave request (employee, web)		●		●			●
D6	Leave approval (Manager)			●				●
D7	Leave cancellation			●	●
D8	Leave request on behalf of employee (Manager)			●
D9	Comp-off request (employee) and approval (manager)			●	●			●
D10	Comp-off request on behalf of employee (Manager)			●
D11	Optional holiday request (employee), approval and on-behalf (manager)		●	●	●
D12	Holiday list and calendar (employee)				●
D13	Leave balance and Company Leave Policies (employee view)				●
D14	Leave reports (Manager)			●
D15	CRM leave request (Sales Executive, web and mobile)		●	●		●				●
E1	EPF configuration		●
E2	ESI configuration		●
E3	Pay Schedule configuration		●	●
E4	Pay group create, configure, activate		●
E5	Assign Pay Group			●
E6	Reassign Pay Group (new financial year, increments)			●
E7	Monthly payroll generation			●	●
E8	Arrear distribution and history		●
E9	TDS distribution			●
E10	Variable pay distribution and schedule		●	●
E11	Payroll Policies configuration		●
E12	Variable DA configuration		●
E13	Bank Master		●
E14	Other Deductions and mapping to pay groups			●
E15	Employee views payslip, CTC history, dashboard				●			●
E16	Advance salary request		●	●	●
E17	Bank wise salary summary			●
E18	Payroll reports	●	●	●
F1	Exit settings (Admin)		●
F2	Separation request, approval, offboarding checklist (end-to-end)			●	●
F3	Termination and termination checklist			●
F4	Other exit-related documentation	●	●		●
G1	Claim request with bills (web, Employee)				●
G2	Claim verification (Manager) and approval and payment (Finance Manager), web		●	●
G3	Claim (mobile): request, verify, approve, pay										●
G4	Claims dashboard (all roles with the module)				●
H1	Timesheet setup chain (Admin): client, project, assign team, task, roles		●
H2	Task and Assign Task (Manager)			●
H3	Submit timesheet (Employee)				●
H4	Timesheet approval (Manager)			●
H5	Defaulters notification			●
H6	Timesheet dashboards and summary (all roles)	●	●	●	●
I1	CRM masters (Admin): Demo Status, Status Master, Associate Types, Qualifications, Specializations		●
I2	CRM leave policies (Admin)		●
I3	Add client to activity to payment (Sales Executive, web)			●		●
I4	Manager view of clients, reassignment			●
I5	Client Associates (mobile)		●							●
I6	Client Payments (mobile)									●
I7	Team Travel Approvals: Pending, Verified, Approved, Claimed			●		●				●
I8	Mobile CRM daily field flow: punch, client, activity									●
I9	Device approvals	●		●
I10	GPS monitoring and tracking reports			●						●
I11	Sales Manager reports and CRM attendance (web)		●	●
I12	Remaining CRM items			●		●				●
J1	Attendance request (employee) and approval (manager), Spryple HCM							●
J2	Leave and comp-off (mobile HCM)							●
J3	Mobile payslip view							●
J4	Rewards and Recognition (send and receive)							●
J5	Mobile HCM manager reports							●	●
J6	Spryple Lite: add employee and configure user								●
J7	Mobile app installation and access							●			●
J8	Mobile punch with camera (CRM)									●
K1	Course builder to course saved (LMS Instructor)						●
K2	Employee course enrolment, assessment, certificate				●
K3	Learning Sphere and badges (employee)				●
K4	Instructor dashboard and reports						●
K5	Manager and Admin LMS views		●	●
K6	LMS access note
L1	HR Policies configuration		●
L2	Onboarding Settings and Offboarding Settings		●
L3	Work Location		●
L4	Department and Designation		●
L5	Holidays		●
L6	Checklist (onboarding and offboarding masters)		●
L7	Induction types		●
L8	Announcements lifecycle (Admin)		●		●
L9	Company Information and Company Logo		●
L10	Messages Master (Admin), and other message masters		●
L11	Overtime duration		●
L12	Finance Admin setup order in the documentation		●
L13	Super Admin dashboard	●
L14	Main dashboard alerts				●

Part 2: Workflows per app

Web: Super Admin (7)

A1 Login (web, Employee / Super Admin) · C19 Attendance report retrieval (Super Admin, Admin, Manager, Employee) · E18 Payroll reports · F4 Other exit-related documentation · H6 Timesheet dashboards and summary (all roles) · I9 Device approvals · L13 Super Admin dashboard

Web: Admin (58)

A2 Users Login creation (Admin creates credentials) · A3 Employee Password Reset (Admin) · A4 Change Password (Employee) · A5 Employee profile edit and picture upload · B1 New hire to first login (end-to-end) · B4 Onboarding checklist assignment · B6 Induction program (HR manager) · B9 Employee Department and Designation mapping · C1 Biometric ID mapping · C6 Permission request (employee) and approval (manager) · C7 Attendance regularization (employee) · C9 Shift creation and assignment (Admin, Manager) · C10 Week-off configuration · C15 Geo-location (branch location) configuration · C16 Extra Days Slab configuration and penalty designations (Admin) · C18 Missed Punch report and default punch-out · C19 Attendance report retrieval (Super Admin, Admin, Manager, Employee) · C20 Attendance Messages Master (Admin) · D1 Leave policy activation (default leaves) · D2 Leave policy deactivation · D3 Common leave rules configuration · D4 Leave type configuration (per type) and Advanced leave · D5 Leave request (employee, web) · D11 Optional holiday request (employee), approval and on-behalf (manager) · D15 CRM leave request (Sales Executive, web and mobile) · E1 EPF configuration · E2 ESI configuration · E3 Pay Schedule configuration · E4 Pay group create, configure, activate · E8 Arrear distribution and history · E10 Variable pay distribution and schedule · E11 Payroll Policies configuration · E12 Variable DA configuration · E13 Bank Master · E16 Advance salary request · E18 Payroll reports · F1 Exit settings (Admin) · F4 Other exit-related documentation · G2 Claim verification (Manager) and approval and payment (Finance Manager), web · H1 Timesheet setup chain (Admin): client, project, assign team, task, roles · H6 Timesheet dashboards and summary (all roles) · I1 CRM masters (Admin): Demo Status, Status Master, Associate Types, Qualifications, Specializations · I2 CRM leave policies (Admin) · I5 Client Associates (mobile) · I11 Sales Manager reports and CRM attendance (web) · K5 Manager and Admin LMS views · L1 HR Policies configuration · L2 Onboarding Settings and Offboarding Settings · L3 Work Location · L4 Department and Designation · L5 Holidays · L6 Checklist (onboarding and offboarding masters) · L7 Induction types · L8 Announcements lifecycle (Admin) · L9 Company Information and Company Logo · L10 Messages Master (Admin), and other message masters · L11 Overtime duration · L12 Finance Admin setup order in the documentation

Web: Managers (57)

A1 Login (web, Employee / Super Admin) · A2 Users Login creation (Admin creates credentials) · A6 Employee onboarding checklist view · B1 New hire to first login (end-to-end) · B2 Employee Directory maintenance · B3 Document approval · B4 Onboarding checklist assignment · B5 Onboarding checklist completion and No Due · B6 Induction program (HR manager) · B7 Employee Reports · B8 Excel upload of employees · C3 Attendance request on behalf of employee (Manager) · C4 Attendance request approval (three ways) · C5 Shift change request (employee) and approval with swap (manager) · C6 Permission request (employee) and approval (manager) · C8 Manager attendance regularization and approval · C9 Shift creation and assignment (Admin, Manager) · C10 Week-off configuration · C11 Shift rotation: create sequence, assign, reassign · C12 Excel upload of attendance (Manager) · C17 Extra Days and Penalty Days reports · C18 Missed Punch report and default punch-out · C19 Attendance report retrieval (Super Admin, Admin, Manager, Employee) · C21 Shift wise report · D6 Leave approval (Manager) · D7 Leave cancellation · D8 Leave request on behalf of employee (Manager) · D9 Comp-off request (employee) and approval (manager) · D10 Comp-off request on behalf of employee (Manager) · D11 Optional holiday request (employee), approval and on-behalf (manager) · D14 Leave reports (Manager) · D15 CRM leave request (Sales Executive, web and mobile) · E3 Pay Schedule configuration · E5 Assign Pay Group · E6 Reassign Pay Group (new financial year, increments) · E7 Monthly payroll generation · E9 TDS distribution · E10 Variable pay distribution and schedule · E14 Other Deductions and mapping to pay groups · E16 Advance salary request · E17 Bank wise salary summary · E18 Payroll reports · F2 Separation request, approval, offboarding checklist (end-to-end) · F3 Termination and termination checklist · G2 Claim verification (Manager) and approval and payment (Finance Manager), web · H2 Task and Assign Task (Manager) · H4 Timesheet approval (Manager) · H5 Defaulters notification · H6 Timesheet dashboards and summary (all roles) · I3 Add client to activity to payment (Sales Executive, web) · I4 Manager view of clients, reassignment · I7 Team Travel Approvals: Pending, Verified, Approved, Claimed · I9 Device approvals · I10 GPS monitoring and tracking reports · I11 Sales Manager reports and CRM attendance (web) · I12 Remaining CRM items · K5 Manager and Admin LMS views

Web: Employee (30)

A1 Login (web, Employee / Super Admin) · A4 Change Password (Employee) · A5 Employee profile edit and picture upload · A6 Employee onboarding checklist view · C2 Attendance request by employee (three entry points) · C5 Shift change request (employee) and approval with swap (manager) · C6 Permission request (employee) and approval (manager) · C7 Attendance regularization (employee) · C17 Extra Days and Penalty Days reports · C18 Missed Punch report and default punch-out · C19 Attendance report retrieval (Super Admin, Admin, Manager, Employee) · D5 Leave request (employee, web) · D7 Leave cancellation · D9 Comp-off request (employee) and approval (manager) · D11 Optional holiday request (employee), approval and on-behalf (manager) · D12 Holiday list and calendar (employee) · D13 Leave balance and Company Leave Policies (employee view) · E7 Monthly payroll generation · E15 Employee views payslip, CTC history, dashboard · E16 Advance salary request · F2 Separation request, approval, offboarding checklist (end-to-end) · F4 Other exit-related documentation · G1 Claim request with bills (web, Employee) · G4 Claims dashboard (all roles with the module) · H3 Submit timesheet (Employee) · H6 Timesheet dashboards and summary (all roles) · K2 Employee course enrolment, assessment, certificate · K3 Learning Sphere and badges (employee) · L8 Announcements lifecycle (Admin) · L14 Main dashboard alerts

Web: Employee (Sales CRM) (4)

D15 CRM leave request (Sales Executive, web and mobile) · I3 Add client to activity to payment (Sales Executive, web) · I7 Team Travel Approvals: Pending, Verified, Approved, Claimed · I12 Remaining CRM items

Web: LMS Instructor (2)

K1 Course builder to course saved (LMS Instructor) · K4 Instructor dashboard and reports

Spryple HCM app (16)

A1 Login (web, Employee / Super Admin) · C2 Attendance request by employee (three entry points) · C4 Attendance request approval (three ways) · C13 Face capture and enrolment (mobile HCM and Lite) · C14 Receptionist (front office) check-in and check-out · C15 Geo-location (branch location) configuration · D5 Leave request (employee, web) · D6 Leave approval (Manager) · D9 Comp-off request (employee) and approval (manager) · E15 Employee views payslip, CTC history, dashboard · J1 Attendance request (employee) and approval (manager), Spryple HCM · J2 Leave and comp-off (mobile HCM) · J3 Mobile payslip view · J4 Rewards and Recognition (send and receive) · J5 Mobile HCM manager reports · J7 Mobile app installation and access

Spryple Lite app (4)

C13 Face capture and enrolment (mobile HCM and Lite) · C14 Receptionist (front office) check-in and check-out · J5 Mobile HCM manager reports · J6 Spryple Lite: add employee and configure user

Spryple CRM app (9)

A1 Login (web, Employee / Super Admin) · D15 CRM leave request (Sales Executive, web and mobile) · I5 Client Associates (mobile) · I6 Client Payments (mobile) · I7 Team Travel Approvals: Pending, Verified, Approved, Claimed · I8 Mobile CRM daily field flow: punch, client, activity · I10 GPS monitoring and tracking reports · I12 Remaining CRM items · J8 Mobile punch with camera (CRM)

Claims (mobile) (2)

G3 Claim (mobile): request, verify, approve, pay · J7 Mobile app installation and access

Part 3: Module-wise, step by step

Module: Access and credentials (6 workflows)

ID	Workflow	Actors	Apps	End state
A1	Login (web, Employee / Super Admin)	Employee, Super Admin.	SA, M, E, HCM, CRM	Main dashboard displayed.
A2	Users Login creation (Admin creates credentials)	Admin.	A, M	The new employee logs in to the application with the credentials.
A3	Employee Password Reset (Admin)	Admin. The notifying sender is named as "HR Department".	A	Credentials updated; user mailed.
A4	Change Password (Employee)	Employee.	A, E	—
A5	Employee profile edit and picture upload	Employee.	A, E	Profile updated.
A6	Employee onboarding checklist view	Employee.	M, E	—

Trigger: A user opens the web application.
Actors: Employee, Super Admin.
Steps:
1. Enter Company code, Username/Email and Password and click Login.
2. Super Admin logs in with Company Code, Username, Password.
3. After a successful employee login, the main dashboard is displayed (Employee Card, Company announcements and Alerts).
4. For the manager role, the main dashboard shows basic employee information, Announcements, Alerts and Pending Leave/Attendance requests.
Statuses: Not documented.
Notifications: Not documented.
End state: Main dashboard displayed.
Variants: Mobile apps use Company Code, Username and Password (Spryple HCM) or Company code, Username/Email and Password (Spryple CRM). and
Not documented: Forgot-password flow, lockout, multi-factor authentication, session expiry.
Help Center: Login ↗ · Super Admin Dashboard ↗ · User Login ↗ · Applying Attendance Request by Employee ↗ · 4.1 Login ↗

Trigger: A new employee needs credentials. The documentation states that after HR adds the new hire, an email is sent to Admin to create the credentials.
Actors: Admin.
Steps:
1. Open Users Login. Click the Edit icon; Employee name and Official Email ID are displayed in fields.
2. Add the Username in the User ID field. The password displays by default as "Welcome1!" (the Employee can update the password in the Employee's login).
3. Click Submit to create the user credentials.
4. The employee receives the credentials information.
Statuses: Not documented.
Notifications: The employee receives the credentials information (channel not stated in the text). . The credentials email carries the login URL, Company Code, Username and the password "Welcome1!".
End state: The new employee logs in to the application with the credentials.
Variants: The Roles & Permissions section contains text identical to Users Login (create Username and Password, Edit icon, "Welcome1!"). . No separate role-assignment steps are documented under that heading.
Not documented: How roles are assigned in Roles & Permissions, how Admin is notified beyond the email statement, credential expiry.
Help Center: Employee Directory ↗ · Users Login ↗ · Roles & Permissions ↗

A3. Employee Password Reset (Admin)

Trigger: Admin opens Employee Password Reset.
Actors: Admin. The notifying sender is named as "HR Department".
Steps:
1. Select Location Name, Department Name, Employee Name.
2. Select Reset Option from the dropdown.
3. Option "Username": enter the new username, click Submit. The user receives a Reset username mail from HR Department.
4. Option "Password": enter the New Password, click Submit. The user receives a Reset password mail from HR Department.
5. Option "New Username and Password": enter the new username, the new password is displayed, click Submit. The user receives a Reset username & password mail from HR Department.
Statuses: Not documented.
Notifications: Reset username mail, Reset password mail, Reset username & password mail (one per option).
End state: Credentials updated; user mailed.
Variants: The form also shows "Existing User Name" and "Existing Password" (masked, with an eye toggle). If the employee has no office email, the admin writes down the credentials and shares them manually.
Not documented: Forced change at next login, audit trail.
Help Center: Employee Password Reset ↗

A4. Change Password (Employee)

Trigger: Employee opens the user menu.
Actors: Employee.
Steps:
1. Click the down arrow at the top right corner.
2. Click Change Password; the page is displayed.
3. Enter current password, New password and Confirm Password.
4. Click Submit.
Variants: Password rules (length, case, digits, special characters, history) are set in HR Policies, see L1.
Not documented: Success message, session behaviour after change.
Help Center: Change Password ↗ · HR Policies ↗

A5. Employee profile edit and picture upload

Trigger: Employee opens Edit Profile.
Actors: Employee.
Steps:
1. Click Edit Profile at the top right corner; the edit profile screen is displayed.
2. Update the needed information and click Submit.
3. Optionally upload a profile picture; the uploaded image is displayed on the employee's dashboard.
End state: Profile updated.
Variants: My Profile shows Personal information, Work experience, Bank Details, Family details, Education details, Documents upload; the employee can edit or update the data. . HR Policies has a rule "Is employee details editable by employee" (Yes or No).
Not documented: Whether edits need approval, and which fields are editable when the rule is Yes.
Help Center: Edit Profile ↗ · My Profile ↗ · HR Policies ↗

A6. Employee onboarding checklist view

Trigger: Employee opens Onboarding Checklist in the Employee Management side menu.
Actors: Employee.
Steps: Login, click Employee Management, click Onboarding Checklist; the employee sees the Induction Program (if any) and the Onboarding Checklist with status.
Statuses: Checklist status is Pending or Completed (set by HR manager, see B5).
Not documented: Whether the employee can act on checklist items.
Help Center: Onboarding checklist ↗ · Onboarding Pending Checklist ↗

Module: Employee management and onboarding (9 workflows)

ID	Workflow	Actors	Apps	End state
B1	New hire to first login (end-to-end)	HR manager, new hire (Employee), Admin.	A, M	New employee logs in with credentials.
B2	Employee Directory maintenance	HR manager.	M	—
B3	Document approval	Employee, HR manager (HR).	M	Documents approved. Checklist items for documents are shown with Department and "Approver Name".
B4	Onboarding checklist assignment	HR manager.	A, M	Checklist awaits updating (B5).
B5	Onboarding checklist completion and No Due	HR manager.	M	Employee checklist status Completed; the employee sees it in their login.
B6	Induction program (HR manager)	HR manager; Admin (program types); employees.	A, M	The program details are displayed in the selected employee's login and main dashboard.
B7	Employee Reports	HR manager.	M	—
B8	Excel upload of employees	HR Manager.	M	Data saved in Employee Directory.
B9	Employee Department and Designation mapping	Admin.	A	—

Trigger: HR manager clicks New Hires and the Add icon.
Actors: HR manager, new hire (Employee), Admin.
Steps:
1. Login with HR manager. Click Employee Management, then New Hires in the HR Manager section. Added employees display with status Hired; a Joined or Hired radio button filters the list.
2. Click the Add icon and enter First name, Middle Name, Last name, Email, Hired On, Joining Date, Designation, Mobile Number, Emergency Contact Number. Click Submit.
3. The employee enters basic information through the received link: Personal Information, Contact Information, Family Details, Work Experience, Education Details and requested documents.
4. When the employee has filled all information, the HR manager clicks the Joining Formalities button and the data is saved in Employee Directory.
5. HR manager adds Work Information: Official Email, Employment Type, Employee Role, working location, Designation, Department, reporting manager.
6. HR manager adds Personal Contact Information (Residence Address, Country, State, City, Pin Code) and Family Details (Name, Contact Number, Gender, Relationship, Status; click Add).
7. Click Save after adding all mandatory fields. HR manager can also add Contract/Promotions, Bank Details, Work Experience, Education, Documents Upload.
8. Employee documents go through Document Approval (B3) and the Onboarding checklist runs (B4, B5).
9. After the process, an email is sent to Admin to create the new employee's credentials.
10. Admin creates the credentials (A2); the employee receives them and logs in.
Statuses: New Hires list: Hired, Joined. . Checklist: Pending, Completed.
Notifications: Link to the employee (channel not stated in the text); the link is sent from no-reply@spryple.com with the subject "Welcome to Spryple" and expires after 24 hours. . Email to Admin to create credentials. . Credentials information to the employee. Document approval and rejection emails are in B3. Automatic reminders for pending onboarding checklists are an Admin setting (L2).
End state: New employee logs in with credentials.
Variants: If the employee has no registered email, HR adds the information in "CANDIDATE DATA" in New Hires. . Required fields on the New Hire form: First Name, Last Name, Hired On, Joining Date, Designation, Mobile, Emergency Contact; personal email is optional. . Bulk entry by Excel upload (B9).
Not documented: What the status Joined requires, what happens when the 24-hour link expires, how Hired changes to Joined, the exact trigger for the Admin email beyond "after completion of the entire process", employee ID generation timing (prefix and seed settings are in L3).
Help Center: Adding New Hire ↗ · Employee Directory ↗ · Onboarding Pending Checklist ↗ · Onboarding Settings ↗

B2. Employee Directory maintenance

Trigger: HR manager opens Employee Directory.
Actors: HR manager.
Steps: Add or update Personal Information. Update an employee's role or reporting manager when there are changes. Use the Edit button to update Personal Information, Work Information, Personal Contact Information.
Not documented: Change history, notification to the employee on role or manager change.
Help Center: Employee Directory ↗

B3. Document approval

Trigger: An employee uploads documents.
Actors: Employee, HR manager (HR).
Steps:
1. Employee-uploaded documents appear on the Document approval screen.
2. View a document with the View icon.
3. Click Approve or Reject.
4. If rejected, the employee re-uploads a valid document; on re-upload the HR manager receives an email.
Statuses: Approved, Rejected (as button outcomes). Documents uploaded by HR on behalf of an employee are automatically approved.
Notifications: Email to the employee after approval; email to the employee to re-upload after rejection; email to the HR manager on re-upload.
End state: Documents approved. Checklist items for documents are shown with Department and "Approver Name".
Not documented: Rejection reason capture, limit on re-uploads.
Help Center: Document Approval ↗ · Manager Detailed Report ↗

B4. Onboarding checklist assignment

Trigger: A new employee is added.
Actors: HR manager.
Steps: HR manager checks the employee's Onboarding checklist. All master checklists (Onboarding) are assigned to every new employee.
Statuses: Pending.
Notifications: Automatic reminders to employees about pending onboarding checklists when enabled in Onboarding Settings.
End state: Checklist awaits updating (B5).
Not documented: Per-item owner assignment rules (checklist items show a Department and "Approver Name" in screenshots ).
Help Center: Onboarding Pending Checklist ↗ · Onboarding Settings ↗

B5. Onboarding checklist completion and No Due

Trigger: The checklist process is carried out.
Actors: HR manager.
Steps:
1. After the checklist process, HR manager updates the checklist; all checklists are updated by the HR Manager.
2. When all checklists are closed/done, the No Due button is enabled.
3. HR manager selects the No due option and clicks Submit.
Statuses: Pending to Completed.
Notifications: Not documented.
End state: Employee checklist status Completed; the employee sees it in their login.
Variants: An "Add Comments" box sits beside No Due.
Not documented: Whether completion triggers credential creation or any other step.
Help Center: Onboarding Pending Checklist ↗

B6. Induction program (HR manager)

Trigger: HR manager clicks the add button in Induction Program.
Actors: HR manager; Admin (program types); employees.
Steps:
1. Admin first creates Induction program types (L7).
2. HR manager clicks add, enters the required fields, clicks Submit; the program is added to the table.
3. HR clicks assign; the employee list is displayed; HR selects employees and clicks Submit.
4. HR manager can edit and cancel the program.
Statuses: Program list columns include Status, with example Scheduled; actions are assign, edit, cancel.
Notifications: Selected employees receive an email about the program; employees receive emails on updated and cancelled programs.
End state: The program details are displayed in the selected employee's login and main dashboard.
Variants: Employee sees Induction Program in the Onboarding Checklist page (A6). The list shows Program Type, Department, Conduct By, Date, Start/End Time, Status.
Not documented: Attendance or completion tracking for the program, status values other than Scheduled.
Help Center: Induction ↗ · Induction Program ↗

B7. Employee Reports

Trigger: HR manager opens Employee Reports.
Actors: HR manager.
Steps: Select column names with the column button; reports are produced from the selection; download with the download button.
Variants: Columns seen in screenshots include Emp ID, Name, Office Email, Mobile, Emp Status, Emp Type, Department, Designation, Location, Gender, Blood group.
Help Center: Employee Reports ↗

B8. Excel upload of employees

Trigger: HR Manager dumps multiple employees' data.
Actors: HR Manager.
Steps: Click Select File and upload the Excel file; the data is saved in the employee directory; HR manager can also download the data with the download button.
End state: Data saved in Employee Directory.
Not documented: Template, validation errors, partial failures, whether credentials are created.
Help Center: Excel Upload ↗

B9. Employee Department and Designation mapping

Trigger: HR Policies rule 36 "Is mapping required between departments & designations?" is Yes.
Actors: Admin.
Steps: Select Department, select Designation, click submit; departments can be searched with designation.
Help Center: HR Policies ↗ · Department Designation Mapping ↗

Module: Attendance (21 workflows)

ID	Workflow	Actors	Apps	End state
C1	Biometric ID mapping	Admin.	A	Employee Bio-metric punches are recorded and the employee can see them on the employee Dashboard.
C2	Attendance request by employee (three entry points)	Employee; Reporting manager (approver, see C4).	E, HCM	Approved or Rejected by the manager.
C3	Attendance request on behalf of employee (Manager)	Manager.	M	Approved.
C4	Attendance request approval (three ways)	Reporting manager / Manager.	M, HCM	Approved or Rejected; the employee can view it.
C5	Shift change request (employee) and approval with swap (manager)	Employee; Manager (Reporting manager).	M, E	Approved or Rejected.
C6	Permission request (employee) and approval (manager)	Employee; Manager.	A, M, E	—
C7	Attendance regularization (employee)	Employee.	A, E	—
C8	Manager attendance regularization and approval	Manager.	M	—
C9	Shift creation and assignment (Admin, Manager)	Admin (create shift); Manager (assign).	A, M	—
C10	Week-off configuration	Manager.	A, M	—
C11	Shift rotation: create sequence, assign, reassign	Manager.	M	—
C12	Excel upload of attendance (Manager)	Manager.	M	—
C13	Face capture and enrolment (mobile HCM and Lite)	Manager; employee (Lite self check-in).	HCM, Lite	—
C14	Receptionist (front office) check-in and check-out	Receptionist.	HCM, Lite	—
C15	Geo-location (branch location) configuration	Manager.	A, HCM	—
C16	Extra Days Slab configuration and penalty designations (Admin)	Admin.	A	—
C17	Extra Days and Penalty Days reports	Employee, Manager (same text on both pages).	M, E	—
C18	Missed Punch report and default punch-out	—	A, M, E	—
C19	Attendance report retrieval (Super Admin, Admin, Manager, Employee)	—	SA, A, M, E	—
C20	Attendance Messages Master (Admin)	—	A	—
C21	Shift wise report	—	M	—

C1. Biometric ID mapping

Trigger: Biometric punches must reach the application. The page states that the admin must map the employee Id and the Bio-metric id.
Actors: Admin.
Steps:
1. Open the Mapping Id's page in the Attendance module.
2. Enter the Bio metric id and select the Employee name.
3. Click Submit to save.
End state: Employee Bio-metric punches are recorded and the employee can see them on the employee Dashboard.
Variants: Punch records carry a Source (examples "Lite", "CRM", "MOBILEAPP").
Not documented: Device integration steps, bulk mapping, unmapping.
Help Center: Mapping ID's ↗

C2. Attendance request by employee (three entry points)

Trigger: An employee has pending or missing attendance. The documentation lists three ways to mark an attendance request: From Main Dashboard, Dashboard, Attendance Request.
Actors: Employee; Reporting manager (approver, see C4).
Steps:
1. Way 1, Main Dashboard: the employee sees pending attendance requests in the Alerts section, can submit an attendance or leave request for pending days; clicking the attendance request icon opens the Attendance request page.
2. Way 2, Dashboard: the employee sees "Send a request" under "Pending Attendance". Clicking it opens the Attendance Request page. Select Work type, From date and To date (default to the pending date and disabled), enter Reason, select Attachment (if any), click Submit.
3. Way 3, Attendance Request in the Attendance Module: select Work type (Work From Home, Work From Office, On-Duty, Work From Remote Location), From date, To date, Reason; tick First Half and/or Second Half; upload attachment; click Submit.
4. Before approval or rejection, the employee can edit (update work type, dates, reason, attachment; click Update) or delete (confirm Yes) the request. ,
5. After a decision, the employee views details with the View icon.
Statuses: Submitted (until the manager acts), Approved, Rejected, Deleted.
Notifications: Not documented for the web flow. Mobile shows a confirmation message "Attendance Request Applied Successfully".
End state: Approved or Rejected by the manager.
Variants: Mobile (J1): Work Type, From Date, To Date, reason. Mobile attendance request also has half-day checkboxes and a required Shift. . On behalf of employee: C3. Approval: C4.
Not documented: Escalation if the manager does not act, notification to the manager.
Help Center: Requesting Attendance ↗ · From Main Dashboard ↗ · Send a request ↗ · Attendance Request ↗ · Edit Request ↗ · Delete Request ↗ …

C3. Attendance request on behalf of employee (Manager)

Trigger: Manager uses "Add a request" on the dashboard or "Request Behalf of Employee" in the side navigation.
Actors: Manager.
Steps:
1. Dashboard route: click "Add a request" under "Request Behalf of Employee"; Employee Name, From date and To date are displayed and disabled by default; select Work type, enter Reason, add attachment, click Submit.
2. Side navigation route: select Employee Name, Work type, From and To dates, enter Reason, add attachment, click Submit.
3. After submission the manager can see the records on the same page.
Statuses: The request is "submitted and approved" on submit.
Notifications: Not documented.
End state: Approved.
Not documented: Employee notification, limits on dates.
Help Center: Managers ↗ · 1)Add a request (Dashboard) ↗ · 2)Request Behalf of Employee (Side Navigation) ↗

C4. Attendance request approval (three ways)

Trigger: An employee's request is in Submitted status.
Actors: Reporting manager / Manager.
Steps: Team option in Main Dashboard; Approve request (Dashboard); Pending Approvals.
1. Way 1: approve the team attendance and leave request from the team option in the main dashboard; clicking "Approve attendance" opens the Approval for attendance page where the Reporting manager can approve or reject.
2. Way 2: click "Approve request"; the Approval for Attendance page shows data with all fields disabled and Approve and Reject buttons. Approve opens an Approval popup; Submit approves. Reject opens a Reject popup; enter the reason; Submit rejects.
3. Way 3: click "Pending Approvals"; the table shows requests with status "Submitted"; click Approve or Reject, or the View icon to open the Approval for Attendance page. Approve and Reject follow the same popups.
Statuses: Submitted to Approved or Rejected.
Notifications: Mobile: "Attendance Request Approved Successfully" or "Attendance Request Rejected Successfully", and the status changes in the employee's login. . Web: Not documented.
End state: Approved or Rejected; the employee can view it.
Variants: Mobile approval (J1). Approval History shows approved and rejected attendance requests with a view button.
Not documented: Bulk approval for attendance requests, multi-level approval.
Help Center: Managers ↗ · 1) Approve from Main Dashboard ↗ · 2) Approve request (Dashboard) ↗ · 3) Pending Approvals (Side Navigation) ↗ · Approving Attendance Request by Manager ↗ · Approval History ↗ …

C5. Shift change request (employee) and approval with swap (manager)

Trigger: An employee with an assigned shift clicks add.
Actors: Employee; Manager (Reporting manager).
Steps:
1. Employee: click add to send a shift change request to the Reporting manager. An assigned shift is required. Applied date is displayed and disabled; select From date and To date; the From Shift is displayed based on dates; select To Shift; enter Reason; click Submit.
2. The employee can edit or delete the record, and view Approved, Rejected, Deleted records.
3. Manager: open Approve Shift Change Request under manager screens; the applied requests are displayed; view full information with the view button.
4. Manager selects an employee from the dropdown to swap shift between employees, and clicks Approve; or clicks Reject.
Statuses: Submitted, Approved, Rejected, Deleted.
Notifications: Not documented.
End state: Approved or Rejected.
Not documented: Whether selecting a swap employee is mandatory, how the swapped employee is informed, rejection reason capture.
Help Center: Shift Change Request ↗ · Approve Shift Change Request ↗

C6. Permission request (employee) and approval (manager)

Trigger: An employee adds a new permission request for the present day or future days.
Actors: Employee; Manager.
Steps:
1. Employee: click add new, select a date, enter permission duration in minutes, enter Reason, click Submit. Multiple permission requests for a day are not allowed.
2. Employee can edit or delete; can cancel an approved record with the cancel icon.
3. Manager: open Approve Permission; submitted requests display in a table; the manager can edit a record (save or cancel the edit), click the approve icon or the reject icon.
4. Permission History shows the outcome.
Statuses: Submitted, Approved, Rejected, Deleted (employee deleted a submitted request), cancelled (employee cancelled after approval).
Notifications: Not documented.
Variants: HR Policies rule 29: consider an employee permission a paid permission or not.
Not documented: Maximum duration, rejection reason capture.
Help Center: Request Permission ↗ · Approve Permission ↗ · Permission History ↗ · HR Policies ↗

C7. Attendance regularization (employee)

Trigger: An employee checked in but did not check out; the record is displayed in the attendance regularization table.
Actors: Employee.
Steps:
1. Click the edit icon on the record; enter the out time; click the save icon (the record is removed from the table) or the cancel icon.
2. Alternatively click the leave request icon; select the leave type (regular leaves display if the employee has them, otherwise only Loss of Pay); From date and To date display by default; the leave count displays; click Submit. After submit the leave is applied and the record is removed from regularization.
Variants: HR Policies rules 32 and 33: option to mark a regularization record as week off; how many past days are displayed.
Not documented: Whether the out-time edit needs manager approval, which statuses apply to the resulting leave.
Help Center: Attendance Regularization ↗ · HR Policies ↗

C8. Manager attendance regularization and approval

Trigger: Manager opens Manager Attendance Regularization; records of that manager's assigned employees display.
Actors: Manager.
Steps:
1. Click the Full Day radio button to list employees marked fully absent or single punch in; multi-selection is supported.
2. Click the attendance request icon to submit attendance; click the leave request icon and a confirmation message "Click on 'Yes' to submit and approve the leave request." is shown.
3. Click Half Day radio button for the Half Day present list; click Half Day Regularization icon; choose Attendance to submit an attendance request or Leave to submit a leave request.
4. Regularization Approval: select multiple records at a time; click the approve icon or the reject icon.
Not documented: Who sees records pending in Regularization Approval versus those the manager submits.
Help Center: Manager Attendance Regularization ↗ · Regularization Approval ↗

C9. Shift creation and assignment (Admin, Manager)

Trigger: Admin creates shifts; a manager assigns shifts and week offs.
Actors: Admin (create shift); Manager (assign).
Steps:
1. Admin: enter Shift Name and Shift Description; select Start Time and End Time (Total Hours auto populates); set Grace Period In Time and Out Time, "Number of lates is more than" and "Deduct leave count"; after submit the shift is listed. Shifts can be set inactive.
2. Manager (Shift configuration): select Shift, Shift duration (From date and To date), select week offs, select Employees, click submit.
3. CRM Manager Configure Shift: same, plus shift history by view icon.
Statuses: Active and Inactive shifts.
Variants: HR Policies rules 19 to 21, 25 and 26 automatically assign a shift to unassigned employees.
Not documented: Conflict handling when assigning overlapping dates.
Help Center: Shift ↗ · Shift configuration ↗ · 1.13 Configure Shift ↗ · HR Policies ↗

C10. Week-off configuration

Trigger: Manager opens week off configuration in the side navigation.
Actors: Manager.
Steps: View an employee's week off details with the view icon, then click close; tick the weekly off check box for the day needed; tick the check box in the table to assign week offs to employees; click submit. . The same steps are listed for Admin.
Variants: CRM Manager: Select Weekly Off, Select Employees, submit; Week off history by view icon. . Default week offs 1 to 3 are HR Policies rules 16 to 18.
Help Center: Week off configuration ↗ · Week off configuration ↗ · 1.14 Week off Configuration ↗ · HR Policies ↗

C11. Shift rotation: create sequence, assign, reassign

Trigger: Manager opens Shift rotation Sequences and clicks add.
Actors: Manager.
Steps:
1. Create: location name displays by default; enter Rotation name; in "Please select shift" only admin-created shifts display; selected shifts display in shift order; a shift can be deleted with the delete icon; click submit; the rotation name with shift order displays in the table.
2. Assign: click assign rotation shift, click add, select location then rotation shift (table displays), select rotation shift, tick check box, click submit. Employees without a rotation shift assigned display in the table.
3. Reassign: select location then rotation shift (table displays), select rotation shift, select start shift, select applicable date in calendar, tick check box, click submit.
Not documented: Rotation interval, how the sequence advances automatically.
Help Center: Shift rotation Sequences ↗ · Assign Rotation Shift ↗ · Reassign Rotation Shift ↗

C12. Excel upload of attendance (Manager)

Trigger: Manager clicks Excel Upload in the left menu.
Actors: Manager.
Steps: Click "select a file"; the file explorer opens; select the file and click Open; the file information shows in a table; click "submit" and the data is saved.
Variants: The Sales Manager web menu also has Excel Upload.
Help Center: Excel Upload ↗

C13. Face capture and enrolment (mobile HCM and Lite)

Trigger: Manager opens Capture Employee Image (Spryple HCM) or Configure User (Spryple Lite).
Actors: Manager; employee (Lite self check-in).
Steps:
1. The manager configures employees' facial recognition profiles.
2. If an employee's facial recognition is uploaded the status is "Verified", else "Not Verified".
3. The view icon shows the captured image; Recapture updates it; the existing image can be deleted and captured again.
4. In Lite: the manager edits employees and manages facial profiles; camera permission is needed.
5. Self check-in: the employee, in the HCM app, can self-check in or check out with face configuration and see timings in the web dashboard.
Statuses: Verified, Not Verified.
Notifications: Not documented.
Variants: A manager or receptionist enrols the face; the kiosk "Face Detections" screen offers All or Select employees, a camera preview, Capture and camera flip. No liveness or anti-spoof cue is visible in screenshots.
Not documented: Matching threshold, retention of images, re-enrolment rules.
Help Center: Capture Employee Image ↗ · 4.1.2 Configure User ↗ · Applying Attendance Request by Employee ↗

C14. Receptionist (front office) check-in and check-out

Trigger: Receptionist logs in.
Actors: Receptionist.
Steps:
1. Login with valid receptionist credentials so that added Employees can check in and check out in the configured geo location, with Front Office Check In or Front Office Check Out.
2. Click Front Office check In; click the All employees radio button and employees capture their attendance.
3. Or click the Select employees radio button, search, and capture the employee attendance.
Variants: Spryple Lite Receptionist Login: login so that added employees can check in and check out.
Help Center: Attendance captured by employees in Receptionist Login ↗ · 4.5 Receptionist Login ↗

C15. Geo-location (branch location) configuration

Trigger: Manager opens Configure Location in the mobile app.
Actors: Manager.
Steps: The manager configures the location; employees can check in and check out based on the configured geo location.
Variants: A per-branch "Branch Location" screen has a Geo fencing Radius (200 m in the example; the options are not shown). . The work location form on web has address and prefix fields (L3).
Not documented: Steps to set the radius, behaviour when a punch is outside the radius.
Help Center: Configure Location ↗ · Work Location ↗

C16. Extra Days Slab configuration and penalty designations (Admin)

Trigger: Admin opens the extra days configuration tab.
Actors: Admin.
Steps:
1. Click Add New; select Designation; enter Minimum days worked, Maximum days worked, Eligible Extra days; click add; the slab displays.
2. The delete icon deletes the slab; the submit button puts the data in a table; the edit icon edits; update saves.
3. Applicable Designations for Penalty: a table lists admin-added designations as Active or Inactive; the user can activate or deactivate designations.
Statuses: Active, Inactive (designations).
Variants: HR Policies rules 43 to 48 configure extra-day payment and week-off penalty.
Help Center: Extra Days Slab configuration ↗ · Applicable Designations for Penalty ↗ · HR Policies ↗

C17. Extra Days and Penalty Days reports

Actors: Employee, Manager (same text on both pages).
Steps: Click the extradays radio button; select the month; click search; based on the pay schedule window extra days display (weekoff present days, Holiday present days, slab count); download PDF and Excel; search with Emp ID and Emp Name; Clear resets to the current month. Penalty Days radio button works the same and shows late attendance and week off absent deduction penalty days. ,
Help Center: Extra Days & Penalty Report ↗ · Extra Days & Penalty Report ↗

C18. Missed Punch report and default punch-out

Steps: Select Month and Year; select Location (Admin) and Employee Name (All Employees or one); search by employee name or ID; download Excel. . Manager sees only assigned employees. . Employee selects the month and clicks search.
Help Center: Missed Punch Report ↗ · Missed Punch Report ↗ · Missed Punch Report ↗ · HR Policies ↗

C19. Attendance report retrieval (Super Admin, Admin, Manager, Employee)

Steps: Select City-Branch, Manager, From and To dates, click Search; open Details to see punch in/out timings, Source Name and Images. Reports: Monthly Attendance, Monthly Shifts, Attendance Summary, Current Day Attendance, Punch Summary. and the sibling sections
Statuses: Day-status legend A, P, W, L, H, HD, WP, HP, HL.
Help Center: Attendance Summary Report ↗ · Monthly Shifts Report ↗ · Monthly Detail Report ↗ · Late Attendance Report ↗ · Overtime Report ↗

C20. Attendance Messages Master (Admin)

Steps: Error and success messages are displayed with screen names; click Edit, edit the message, click save.
Help Center: Attendance Messages Master ↗

C21. Shift wise report

Steps: The Reporting manager selects a period; view button shows the list of attendance for the current date with S.No, Shift, Employee name and Status.
Help Center: Shift wise Report ↗

Module: Leave (15 workflows)

ID	Workflow	Actors	Apps	End state
D1	Leave policy activation (default leaves)	Admin.	A	Activated leave policies display on the leave policies page.
D2	Leave policy deactivation	—	A	—
D3	Common leave rules configuration	—	A	—
D4	Leave type configuration (per type) and Advanced leave	—	A	—
D5	Leave request (employee, web)	Employee; Manager (decision, D6).	A, E, HCM	Approved or Rejected by manager.
D6	Leave approval (Manager)	Manager.	M, HCM	—
D7	Leave cancellation	Employee; Manager.	M, E	—
D8	Leave request on behalf of employee (Manager)	—	M	—
D9	Comp-off request (employee) and approval (manager)	Employee; Manager.	M, E, HCM	—
D10	Comp-off request on behalf of employee (Manager)	—	M	—
D11	Optional holiday request (employee), approval and on-behalf (manager)	Employee; Manager.	A, M, E	—
D12	Holiday list and calendar (employee)	—	E	—
D13	Leave balance and Company Leave Policies (employee view)	—	E	—
D14	Leave reports (Manager)	—	M	—
D15	CRM leave request (Sales Executive, web and mobile)	—	A, M, E-CRM, CRM	—

D1. Leave policy activation (default leaves)

Trigger: Admin opens the Leave policies page after logging in.
Actors: Admin.
Steps:
1. Click Add new; all deactivated leave policies are displayed.
2. Select one leave policy and click submit to activate it.
Statuses: Activated, deactivated policies. Ten leave types exist: Casual, Sick, Comp-off, Loss of pay, Maternity, Paternity, Wedding, Bereavement, Earned, Advanced.
End state: Activated leave policies display on the leave policies page.
Help Center: Leave Policies ↗ · How to activate default leaves ↗

D2. Leave policy deactivation

Steps: Click Edit on a leave policy (example Loss of Pay Leave); click the Deactivate button; the leave type no longer displays in the leave policies table. The same applies to other leave types.
Help Center: How to deactivate Default leaves ↗

D3. Common leave rules configuration

Steps: Click Edit on common rules; set the six rules; click Save.
Notifications: Rule 4 controls whether mails are sent on submit, approve, reject. Mail content and recipients are Not documented.
Help Center: Common rules configuration ↗

D4. Leave type configuration (per type) and Advanced leave

Trigger: Admin clicks Edit on a leave policy, sets rules, clicks submit.
Help Center: Casual leave Configuration ↗ · Sick leave Configuration ↗ · Comp-off leave Configuration ↗ · Loss of pay Leave Configuration ↗ · Maternity Leave Configuration ↗ · Paternity Leave Configuration ↗ …

D5. Leave request (employee, web)

Trigger: Employee clicks Leave Request in the Leave Management module.
Actors: Employee; Manager (decision, D6).
Steps:
1. Select leave type based on available leave balance; select From date and To date (past dates based on configuration, and future dates); select second half and first half as required.
2. Leave count displays automatically; enter reason; click Submit.
3. Sandwich leave rules apply as configured by Admin (Friday and Monday week-offs; days before and after a company holiday).
4. In Leave History the employee can view, edit and delete the request before manager approval; can delete past or future requests before approval.
Statuses: submitted, approved, rejected, deleted. . CRM leave history statuses: Approved, Rejected, Deleted, Cancelled. . A status "Cancel Submitted" is also shown.
Notifications: Mail on submit/approve/reject is controlled by common rule 4 (D3). Mobile: "Leave Request Submitted Successfully".
End state: Approved or Rejected by manager.
Variants: Mobile (J2) also captures Contact Number and Emergency Mail during leave. . Sick leave can need supporting document upload. . On behalf: D8.
Not documented: Balance deduction timing, handling when the balance is insufficient (apart from the regularization note that Loss of Pay is offered when no regular leaves exist).
Help Center: Leave Request ↗ · Leave History ↗ · Applying Leave Request by Employee ↗ · Sick leave Configuration ↗

D6. Leave approval (Manager)

Trigger: Leave requests are pending in the Manager Leave Dashboard.
Actors: Manager.
Steps:
1. Pending Requests lists the latest leave requests; the manager can Approve, Reject, View.
2. Approve: click approve.
3. Reject: click Reject, enter the reason for rejecting, click Submit.
4. Review and approve: approve or reject by clicking approve.
Statuses: Approved, Rejected, Deleted (Leave History).
Notifications: Mobile: "Leave Request Approved Successfully" or "Leave Request Rejected Successfully", status changes in the employee's login.
Variants: CRM Manager: Leave Approvals (Approve, Reject, View). . Calendar shows employees who applied and were approved.
Not documented: Delegation, auto-approval timeouts.
Help Center: Pending Requests ↗ · Approve ↗ · Reject ↗ · Review & approve ↗ · Leave History ↗ · Approving Leave Request by Manager ↗ …

D7. Leave cancellation

Trigger: An employee wants to cancel an approved future leave.
Actors: Employee; Manager.
Steps:
1. Employee cancels the approved future leave after manager approval.
2. Employee cannot cancel past leaves, before or after approval.
3. Manager: Pending Cancellation Requests lists the latest cancelled requests; the manager can Approve, Reject and View the cancellation.
Statuses: "Cancel Submitted" ; Cancelled .
Not documented: Balance restoration, effect on payroll.
Help Center: Leave History ↗ · Pending Cancellation Requests ↗

D8. Leave request on behalf of employee (Manager)

Steps: Click request on behalf of an employee in the left menu; available leave balance displays for the selected employee; select employee name, available leave type, from date and to date; leave count displays; enter reason; click submit. After submitting, the request is auto approved.
Statuses: auto approved. Notifications / Not documented: Not documented.
Help Center: Request on Behalf of Employee ↗

D9. Comp-off request (employee) and approval (manager)

Trigger: Employee opens Comp-Off Request in the Leave module.
Actors: Employee; Manager.
Steps:
1. Select Worked date from the calendar (only week-off dates and Holiday dates are enabled), worked Hours, Minutes, enter Reason; the employee can apply comp-off before the upcoming week-off; click submit.
2. Manager: Pending Comp-off lists the latest comp-off requests; Approve, Reject and View.
3. Comp-off History lists approved, Utilized, Expired requests.
Statuses: submitted, approved, rejected (mobile); Approved, Utilized, Expired. ,
Notifications: Mobile: "Comp-Off Request Submitted Successfully", "Comp-Off Request Approved Successfully", rejection equivalent.
Variants: Policy rules (minimum hours, backdated days, lapse days) are in D4. Mobile approval menu: Comp-Off Approvals.
Not documented: How an approved comp-off becomes a leave day, and what moves it to Utilized or Expired.
Help Center: Comp-off Request ↗ · Pending Comp-off ↗ · Comp-off History ↗ · Applying Comp-Off Request by Employee ↗ · Approving Comp-Off Request by Manager ↗

D10. Comp-off request on behalf of employee (Manager)

Steps: Select Employee Name; select Worked Date (worked dates on week offs and holidays display); select Leave Date; enter Reason; click submit; the comp off is applied.
Help Center: Comp off Request on Behalf of Employee ↗

D11. Optional holiday request (employee), approval and on-behalf (manager)

Trigger: Employee opens Optional Holiday Request.
Actors: Employee; Manager.
Steps:
1. Employee: click add; select the optional holiday from the dropdown; enter remarks; click submit. The employee can delete and view records. By default current month dates display; past months can be selected.
2. Manager (Optional Holiday Approval): requests appear in the "optional holiday pending approval screen"; select From and To date; search; pending records display by default.
3. Approve: the approved status displays in the employee screen and the manager approved list table.
4. Reject: click Reject, enter the reject reason, click Submit; the reject status displays in the employee login and the manager Rejected table.
5. On behalf: click the button, select Employee Name, Optional Holiday, enter Remarks, click submit; Approved records display in the table.
Statuses: Submitted, Approved, Rejected, Deleted.
Variants: The maximum optional holidays per financial year is common rule 6. . Optional holidays are defined by Admin under Holidays (L5).
Help Center: Optional Holiday Request ↗ · Optional Holiday Approval ↗ · Optional Holiday on Behalf of Employee ↗ · Common rules configuration ↗

D12. Holiday list and calendar (employee)

Steps: Click Leave Management; calendar shows holidays, week offs, leaves; the company holiday list shows upcoming 3 holidays on the right; View All shows the whole list.
Not documented: Not applicable beyond display.
Help Center: Holiday List ↗

D13. Leave balance and Company Leave Policies (employee view)

Steps: Leave Balance shows available leave balance. . Company Leave Policies shows common rules and each leave type's policy with all fields disabled (read-only).
Variants: Screenshot shows Used/Available/Total and Manager Name on the request.
Help Center: Leave Balance ↗ · Company Leave Policies ↗

D14. Leave reports (Manager)

Steps: Detailed Report and Employee wise Report: select Employee name (or All), period, leave type, Leave Status and Designation; click search; download Excel and PDF. Summary Report: total worked days and Total Leaves count. Payroll Report: Leaves approved count, Loss of pay count, Absents count; default current month. , ,
Help Center: Employee wise Report ↗ · Summary Report ↗ · Payroll Report ↗

D15. CRM leave request (Sales Executive, web and mobile)

Steps: Apply leave; available leave balance and reporting manager name are displayed; select leave type, From and To date, second half and first half; leave count shows automatically; enter reason; click submit. . History: view, edit, delete before manager approval.
Statuses: applied, approved, rejected, cancel leaves (manager's leave history).
Help Center: 4.5 Leave Request ↗ · 4.6 Leave History ↗ · 5.8.c Pending Approvals ↗ · 5.8.b Leave History ↗ · Finance Admin ↗ · Finance Manager ↗ …

Module: Payroll (18 workflows)

ID	Workflow	Actors	Apps	End state
E1	EPF configuration	—	A	—
E2	ESI configuration	—	A	—
E3	Pay Schedule configuration	—	A, M	—
E4	Pay group create, configure, activate	Finance Admin / Finance Manager.	A	Only active pay groups display in the assign section.
E5	Assign Pay Group	Finance Manager.	M	Employee salary is calculated based on this pay group and components.
E6	Reassign Pay Group (new financial year, increments)	—	M	—
E7	Monthly payroll generation	Finance Manager (only the Finance Manager can generate payslips).	M, E	Salary slips display in the employee login.
E8	Arrear distribution and history	Finance Admin.	A	—
E9	TDS distribution	Finance Manager.	M	—
E10	Variable pay distribution and schedule	Finance Manager.	A, M	—
E11	Payroll Policies configuration	—	A	—
E12	Variable DA configuration	—	A	—
E13	Bank Master	—	A	—
E14	Other Deductions and mapping to pay groups	Finance Manager.	M	—
E15	Employee views payslip, CTC history, dashboard	—	E, HCM	—
E16	Advance salary request	Employee; Finance manager / Manager (decision).	A, M, E	—
E17	Bank wise salary summary	Finance Manager.	M	—
E18	Payroll reports	—	SA, A, M	—

E1. EPF configuration

Trigger: Finance Admin / Finance Manager clicks EPF in the side menu.
Steps: The EPF configuration page displays with default configuration; click Edit; change the rules (Employee contribution, Employer's contribution, Admin charges, EDIL contribution); click save.
Help Center: EPF ↗

E2. ESI configuration

Steps: The ESI configuration page displays defaults; check or uncheck "Include Employer's contribution in the CTC" (the page says that, based on this selection, employees get the ESI amount); add and edit state-wise ESI number.
Help Center: ESI ↗

E3. Pay Schedule configuration

Steps:
1. Open Pay Schedule; the earlier configuration displays; click edit.
2. Same payroll and leave window: select YES (example: salary for the 1st to the last day of the month). Different windows: select No and choose leave window dates (example: previous month 25 to present month 24).
3. Choose how monthly salary is calculated: Actual days in a month, or Organization working days. Click Save.
Help Center: Pay Schedule ↗ · Pay Schedule ↗

E4. Pay group create, configure, activate

Trigger: Finance user clicks the add button on the Pay group page.
Actors: Finance Admin / Finance Manager.
Steps:
1. Enter Pay group name, Start range and End range; select Earnings and Deductions; click save. The pay group displays in the table with "configuration in progress" status.
2. Click the Configuration button; the selected components display; click configure to give a percentage or flat amount; the Earning request page displays; CTC percentage and Basic salary percentage change automatically with input; click submit.
3. Some components do not allow a flat amount (percentage only; flat amount is disabled). Some components are not eligible for EPF (EPF option disabled). The component name can be changed and reflects in the Pay slip.
4. The pay group status changes from "Configuration in Progress" to "ACTIVE".
Statuses: Configuration in Progress, ACTIVE.
Notifications: Not documented.
End state: Only active pay groups display in the assign section.
Not documented: The exact action that moves the status to ACTIVE beyond configuring components, deactivation or deletion of pay groups, edit rules after activation.
Help Center: Pay group ↗ · Pay group configuration ↗

E5. Assign Pay Group

Actors: Finance Manager.
Steps: Click "Assign Pay Group"; select Employee name, enter Employee CTC, click Search; pay group information based on the CTC displays; select one pay group; a CTC breakdown pop-up shows monthly and annual salary details (changes with EPF configuration); click Assign to save.
End state: Employee salary is calculated based on this pay group and components.
Variants: The Employee Pay Groups grid shows Emp ID, Name, Location, Department, Designation, Pay Group, CTC, Assigned On.
Help Center: Assign Pay Group ↗

E6. Reassign Pay Group (new financial year, increments)

Steps: Two radio options: (1) Change the employee CTC without changing the Pay group: select employee, enter the new CTC, click submit; the employee gets the new CTC with the same previous pay group. (2) Change the employee CTC and Pay group: enter the new CTC, click submit; pay groups created for that CTC display; select one; the new CTC with the new pay group is assigned.
Variants: CTC History shows a "Select Duration" selector.
Help Center: Reassign Pay group ↗

E7. Monthly payroll generation

Trigger: Finance Manager opens the monthly payroll page.
Actors: Finance Manager (only the Finance Manager can generate payslips).
Steps:
1. Select Financial year and month and year; all employee names display.
2. Select at least one employee and click Calculate Salary to generate the salary slip.
3. View generated payroll in Monthly Payroll Report (salary details with bank account information; PDF downloadable to submit to banks).
4. The employee views the payslip in the Payroll Management module (Pay Slips, E15).
Statuses: Not documented as named values for payroll runs.
Notifications: Not documented.
End state: Salary slips display in the employee login.
Variants: Payslip calculations draw on Pay Group configuration and EPF/ESI settings, including Earnings, Deductions, Other Deductions, LOP amount, Arrear amount, Variable Pay amount, Gratuity, OT amount, Extra Days amount. . Payroll Policies govern behaviour (E11).
Not documented: Approval or lock of a payroll run, reversal or re-run, payment disbursement.
Help Center: Monthly Payroll (Generate Payroll) ↗ · Monthly Payroll Report (View generated Payroll) ↗ · Pay Slips ↗

E8. Arrear distribution and history

Actors: Finance Admin.
Steps:
1. Click Arrear Distribution; click Arrear Entry; select Month and Year, City-Branch, Employee Name.
2. Arrear names display in a table; select an arrear name and amount (at least one); tick the check box; click Submit.
3. History: select Month and Year and City-Branch; search by EMP.Name and EMP.ID; saved data displays.
Statuses: Pending, Paid. When the status changes to Paid, the arrear amount also displays in the employee's payslip view screen.
Help Center: Arrear Distribution ↗ · Arrear Distribution History ↗

E9. TDS distribution

Actors: Finance Manager.
Steps: Click TDS Distribution; click TDS Entry; select Month and City-Branch; employee names display; search by name; select the check box and enter the amount; click submit; data saves in TDS History; click TDS History.
Variants: The employee Payroll menu includes IT Declaration and Form 16 in screenshots.
Help Center: TDS Distribution ↗

E10. Variable pay distribution and schedule

Actors: Finance Manager.
Steps:
1. Click Variable pay distribution; click Variable pay entry; select City-Branch, Calculation Period, Distribution period; employee names display; select employees; select the check box and enter the variable pay amount; click submit.
2. Click history; select City-Branch; employee data displays.
3. Variable Pay Schedule: select distribution type Monthly share or Lump sum.
Variants: Payroll Policies rule 12 sets variable pay frequency (Monthly, Quarterly, Half-yearly, Yearly).
Help Center: Variable Pay Distribution ↗ · Variable Pay Schedule ↗ · Payroll Policies ↗

E11. Payroll Policies configuration

Steps: Click Payroll Policies in the Finance admin screen and set 14 rules: advance salary recovery instalments (rule 1), months after last recovery before advance resumes (rule 2), overtime in salary (3), Gratuity Act coverage (4), gratuity in monthly component (5), variable DA applicability (6), absent as LOP (7), dynamic payroll processing (8), its leave threshold (9), ESI and EPF independent of LOP (10), minimum hours for overtime (11), variable pay frequency (12), LOP days for proportionate week off deduction (13), payment for extra working days (14).
Help Center: Payroll Policies ↗

E12. Variable DA configuration

Steps: Click variable DA configuration; click add icon; enter Notification name, Published Name, CPI points, CPI points at notified date, Date, VDA rate per point, Effective date; select attachments (if any); click save. View icon opens a record for editing; update saves; cancel returns to the table without saving.
Help Center: Variable DA Configuration ↗

E13. Bank Master

Steps: Click add; give Bank Name, IFSC Code, Account Number, Address1, Address2; select Country, State, City, Status, Is EPF, Is ESI, Is Professional Tax; click submit; edit then Update to save; submitted data displays in the table.
Statuses: Status field present (values Not documented).
Help Center: Bank Master ↗

E14. Other Deductions and mapping to pay groups

Actors: Finance Manager.
Steps:
1. Other Deductions: click add; enter deduction name and deduction amount; click submit; the row displays with an edit icon; editing allows changing the deduction amount; save.
2. Manage Other Deductions (pay group deduction mapping): click add; select the Pay group and the Deduction; click "Add this Deduction"; the record displays; the Cancel icon removes the record.
Help Center: Other Deductions ↗ · Manage Other Deductions ↗

E15. Employee views payslip, CTC history, dashboard

Steps: Click Payroll Management then the view icon in Dashboard; click View to open the payslip; click the download icon to download. . CTC History shows earning components monthly and annually per Pay group configuration. . Dashboard shows pay slips and EPF deduction amount; ESI deduction if eligible.
Help Center: Pay Slips ↗ · CTC History ↗ · Employee Dashboard ↗ · PAYROLL MANAGEMENT ↗

E16. Advance salary request

Trigger: Employee clicks add on Request Advance Salary. A minimum of 1 month payslip is required.
Actors: Employee; Finance manager / Manager (decision).
Steps:
1. Click add; the Advance salary request screen displays; enter "Required advance payment amount" (up to the Gross Salary only); click submit.
2. Request status displays as "Submitted"; the request displays in the Finance manager login, Advance Salary Approval screen.
3. After approval or rejection the status displays in the request table with applied date, approved date, Recovery Duration, recovered months, recovered balance, pending amount, Recovery status and request status.
Statuses: Submitted, Approved, Rejected. Screenshot sample recovery status "Recovery Not Started"; form fields Request Eligible Amount (read-only) and number of months to recover (default 2).
Notifications: Not documented.
Variants: Payroll Policies rules 1 and 2 govern recovery instalments. . The Advance Salary Report heading has no body text.
Not documented: The approval steps themselves (only the screen name is given), how recovery is deducted, payout.
Help Center: Request Advance Salary ↗ · Payroll Policies ↗ · Advance Salary Report ↗

E17. Bank wise salary summary

Actors: Finance Manager.
Steps: Click bank wise salary summary; click add; select Month and Year and Bank Name; click search; ESI deduction amount, EPF deduction amount and PT amount for all employees display, with Pay group total salary; the check box is disabled when employee salary is pending; select check boxes; the total amount displays; click submit; submitted data displays in the table.
Help Center: Bank Wise Salary Summary ↗ · EPF deduction ↗

E18. Payroll reports

Steps: EPF Report (download to upload on the EPF portal); ESI Report (PDF or Excel); Professional Tax Report (select month and state, search); Professional Tax (View) (ranges and monthly deductions state-wise); Employee Payments Report (City-Branch, Manager, Month and Year); Leave Balance Report; Detailed Payroll Report (previous month default; view icon opens pay slip; download); Employee Pay group List (Location and pay group); Payable Days Report (month, branch, manager). and sibling sections
Help Center: EPF Report ↗ · Employee Pay Group List ↗ · Finance Dashboard ↗ · Payroll Messages Master ↗

Module: Exit management (4 workflows)

ID	Workflow	Actors	Apps	End state
F1	Exit settings (Admin)	—	A	—
F2	Separation request, approval, offboarding checklist (end-to-end)	Employee; HR manager.	M, E	Employee checklist status Completed.
F3	Termination and termination checklist	HR manager.	M	—
F4	Other exit-related documentation	—	SA, A, E	—

F1. Exit settings (Admin)

Steps: Offboarding Settings: enable or disable Send Automatic Reminders (if enabled, reminder messages go to employees about timely completion of the employee clearance form); enable or disable Notice Period (if enabled, a Notice Period (In Days) dropdown displays).
Statuses: Active, Inactive.
Help Center: Offboarding Settings ↗ · Termination Category ↗ · Reason for Separation ↗ · HR Policies ↗

F2. Separation request, approval, offboarding checklist (end-to-end)

Trigger: Employee logs in, clicks Exit Management then Separation.
Actors: Employee; HR manager.
Steps:
1. Click Proceed to submit the Separation Request.
2. Select the request exit date, reason; enter notes about separation; click Submit.
3. The employee can edit, view and cancel the request before the manager's approval.
4. HR manager: the applied employee displays in Separation Pending Approvals; click View for details; approve or reject.
5. To approve: select the Approve Exit Date, enter the reason for approval, click submit. To reject: enter the reason for rejection, click submit.
6. After approval, the approved employee displays in Separation Pending Checklist; all checklists added in the master screen display; the HR manager updates items; when all are closed/done, the "No due" button is enabled; the HR manager selects No due and clicks the button.
Statuses: Submitted, Approved. The same page states, for rejection, "Status is changed from submitted to approved". . Checklist: Pending to Completed.
Notifications: Reminder messages about the employee clearance form, if enabled (F1). Other notifications: Not documented.
End state: Employee checklist status Completed.
Variants: Screenshots show a retention letter before Proceed ("discuss with your Reporting Manager or HR"); form fields Applied Date, Notice Period (30), Relieving Date auto-computed (applied + notice), Requesting Exit Date, Reason (dropdown), Notes.
Not documented: The rejected status value (see source conflict above), what happens to the employee's login and payroll at exit, final settlement.
Help Center: Separation ↗ · Separation pending approvals ↗ · Separation Pending Checklist/Offboarding Pending Checklist ↗

F3. Termination and termination checklist

Trigger: The organization wants to terminate the employee; HR manager clicks the termination button in the exit module.
Actors: HR manager.
Steps:
1. Select employee name and termination category; click terminate.
2. An alert message displays; click Yes for approval, or No to cancel.
3. The terminated employee displays in the Termination Pending Checklist page; the master checklists display; the HR manager updates items; when all are closed/done, the No due button is enabled; select it and click the button.
Statuses: Checklist Pending to Completed.
Notifications: Not documented.
Not documented: Whether the employee receives a notice, effective date entry beyond the HR Policies backdated-days rule 37.
Help Center: Termination ↗

Help Center: Separation ↗ · Checklist ↗ · Super Admin Dashboard ↗

Module: Claims (4 workflows)

ID	Workflow	Actors	Apps	End state
G1	Claim request with bills (web, Employee)	Employee; Manager (verify); Finance Manager (approve, pay).	E	—
G2	Claim verification (Manager) and approval and payment (Finance Manager), web	—	A, M	—
G3	Claim (mobile): request, verify, approve, pay	—	Claims	Paid. All claims reports are in "Claims Report" in the web application.
G4	Claims dashboard (all roles with the module)	—	E	—

G1. Claim request with bills (web, Employee)

Trigger: Employee clicks Claim Request in the Claim Management module.
Actors: Employee; Manager (verify); Finance Manager (approve, pay).
Steps:
1. Click Add (+); the Expense Details popup shows Reimbursement Type, Bill Number, Bill Date, Bill Amount, Choose File; click submit.
2. The details display in the table with Add Expense, Total Requested Amount and Description.
3. Add the Description and click Submit; a success popup displays and the request is submitted.
4. Track under tabs Submitted, In Progress, Paid, Rejected.
Statuses: Submitted (with the manager until reviewed), In Progress (under review by manager or Finance Manager), Paid, Rejected.
Notifications: Not documented for the web flow.
Variants: Claim ID format CL_GEN_<company>_<n>; bill image required with a 2 MB limit. . Mobile: G3.
Not documented: Bill limits per claim, edit or withdrawal after submit.
Help Center: Claims Request ↗

G2. Claim verification (Manager) and approval and payment (Finance Manager), web

Steps:
1. Manager: Claim Approval page with Select Employee, From and To date; tabs Pending, Verified, Approved, Paid, Rejected. A claim waiting for the manager's verification stays under Pending; the View icon opens the claim.
2. Claims verified by the Manager display in Claim Approval for the Finance Manager, with fields City-Branch, Manager, Select Employee, From Date, To Date and tabs Verified, Approved, Paid, Rejected.
3. If the Finance Manager approves, the claim stays under Approved; if settled with the employee, under Paid; if the Manager or Finance Manager rejects, under Rejected.
Statuses: Pending, Verified, Approved, Paid, Rejected. The dashboard "Claims Count by Status" shows Pending, Verified, Approved, Paid, Rejected, Total.
Notifications: Alerts are displayed for the claim requests on the dashboard.
Not documented: The web steps that mark a claim Approved and Paid (the web pages describe tabs, not buttons); rejection reason capture on web (mobile shows a Rejected Reason ); partial approval on web.
Help Center: Claims Approval ↗ · Claim Approval ↗ · Claims Module for Manager ↗

G3. Claim (mobile): request, verify, approve, pay

Trigger: Employee opens More, Claim Management, Claims History, then "Claim Request".
Steps:
1. Applied Date shows the current date; click "Add Bills"; the popup has Bill Date, Reimbursement Type, Bill No., Bill Amount, Upload Image, Add Bill, Clear; click "Add Bill" to save the bill; Total Requested Amount shows the sum; enter Description and click "Save" to submit.
2. Manager: Claims Pending Approvals lists submitted claims (search by name or claim ID); open a claim; Verify and Reject buttons display; a separate Reject button displays for each bill; clicking "Verify" shows "Verified Amount" with Verify and Reject buttons; click verify. Status updates to "Verified" in Claims History in the employee's login.
3. Verified records display in the web application for the Finance Manager; verified claims are approved by the Finance Manager from the web application; approved records can be paid from the Finance Manager login in the web application; later the status updates to "Paid".
Statuses: Submitted, Verified, Paid, Rejected.
Notifications: Not documented.
End state: Paid. All claims reports are in "Claims Report" in the web application.
Variants: A manager can also raise a claim request from Claim History. . Claims is a module inside the HCM/CRM app shell (More, Claims Management).
Not documented: Per-bill rejection outcome on the claim total, mobile Approved status (the mobile list names Submitted, Verified, Paid, Rejected only).
Help Center: Claims Management by Employee ↗ · Claim Pending Approvals ↗ · Claims History ↗

G4. Claims dashboard (all roles with the module)

Steps: Click Claim Management; Employee Dashboard displays by default with Claims Count by Status (Current Month), Settlement Ratio (Claims paid versus Total Claims), Alerts, Claims Scorecard (Total Claims, Approved, Rejected, Paid counts for Previous and Current Months with variance in count and amount), Reimbursement Type by Paid Amount.
Help Center: Claims Module for Employee ↗

Module: Timesheet (6 workflows)

ID	Workflow	Actors	Apps	End state
H1	Timesheet setup chain (Admin): client, project, assign team, task, roles	Admin.	A	Records listed in tables.
H2	Task and Assign Task (Manager)	—	M	—
H3	Submit timesheet (Employee)	—	E	—
H4	Timesheet approval (Manager)	—	M	—
H5	Defaulters notification	—	M	—
H6	Timesheet dashboards and summary (all roles)	—	SA, A, M, E	—

H1. Timesheet setup chain (Admin): client, project, assign team, task, roles

Trigger: Admin login, Time Sheet Management.
Actors: Admin.
Steps:
1. Client: click Add icon; fill Client, Contact Name, Designation, Contact Number, Email, Start Date, Address, Country, State, City, Pin code; click Submit; a success popup displays and the client is added. Status can be Active or Inactive; duplicates are not allowed.
2. Project: Add icon, fill all fields, Submit; Active or Inactive; duplicates not allowed; edit and Submit.
3. Assign Team: Add icon, fill all fields, Submit; Active or Inactive.
4. Task: Add icon, fill all fields, Submit; Active or Inactive; duplicates not allowed; edit with Update.
5. Project Roles: create; duplicates not allowed; edit with Update.
Statuses: Active, Inactive. Project status values appear in the summary report filter (Not documented individually); a sample shows task status "In Progress".
Notifications: Not documented.
End state: Records listed in tables.
Not documented: Order dependencies between these steps (the page lists them in this order only), fields of Project, Assign Team and Task forms ("all fields" is the documentation's wording).
Help Center: 1.1 Client ↗ · 1.2 Project ↗ · 1.3 Assign Team ↗ · 1.4 Task ↗ · 1.5 Project Roles ↗

H2. Task and Assign Task (Manager)

Steps: Task: Add icon, fill all fields, Submit; Active or Inactive; duplicates not allowed; search box. . Assign Task: Add icon, fill all fields, Submit; success popup; edit with Update.
Help Center: 2. Task ↗ · 3. Assign Task ↗

H3. Submit timesheet (Employee)

Trigger: Employee opens Submit Timesheet; two tabs, New Entry and History.
Steps:
1. New Entry shows Date, Project, Task, Description, Hours, %, Task Completed checkbox, with Submit and Clear; fill all fields and click Submit.
2. Add icon adds another record; Minus icon deletes a record.
3. If the HR Policies rule "Do you want to limit the timesheet entry hours to attendance hours of that day?" is Yes, the user must have attendance that day to submit.
4. History shows From Date and To Date (default current week).
Statuses: Pending count displays on the employee dashboard ("Pending timesheet count").
Help Center: 2. Submit Timesheet ↗ · 2.1 New Entry ↗ · 2.2 History ↗ · 1. Employee Dashboard ↗

H4. Timesheet approval (Manager)

Steps: Pending Approvals has four tabs: Pending Request, History, Defaulters, All History. A submitted request waits under Pending Request; the manager approves by selecting the check box and clicking Approve, or by clicking the Approve icon; rejects with the Reject icon.
Statuses: Pending, approved, rejected (as outcomes). Notifications: Not documented. Not documented: Rejection reason, resubmission.
Help Center: 4.1 Pending Request ↗

H5. Defaulters notification

Steps: Employees who have not submitted a timesheet remain under the Defaulters tab; the Send Notification button displays; clicking it sends an email to the employee about the pending request.
Notifications: Email on button click. Not documented: Automatic reminders.
Help Center: 4.3 Defaulters ↗

H6. Timesheet dashboards and summary (all roles)

Steps: Employee Dashboard task summary bars (Assigned tasks and Completed tasks), pending timesheet count. . Manager and Super Admin dashboards: Active Projects, Project Assigned Employees, Bench Employees, pie, donut, bar charts by Date dropdown. ,
Help Center: 1. Employee Dashboard ↗ · 1. Dashboard ↗ · 1. Dashboard ↗ · 2. Summary Report ↗ · 3. Effort Variance Report ↗ · Help › For Admin › CRM Field force management › 1. Sales Admin …

Module: CRM and field force (12 workflows)

ID	Workflow	Actors	Apps	End state
I1	CRM masters (Admin): Demo Status, Status Master, Associate Types, Qualifications, Specializations	—	A	—
I2	CRM leave policies (Admin)	—	A	—
I3	Add client to activity to payment (Sales Executive, web)	Sales Executive / Field executive; Manager (reassignment).	M, E-CRM	—
I4	Manager view of clients, reassignment	—	M	—
I5	Client Associates (mobile)	—	A, CRM	—
I6	Client Payments (mobile)	—	CRM	—
I7	Team Travel Approvals: Pending, Verified, Approved, Claimed	Employee; Manager (verify or reject); Finance Manager (approve).	M, E-CRM, CRM	—
I8	Mobile CRM daily field flow: punch, client, activity	—	CRM	—
I9	Device approvals	Manager (Super Admin page has the same text).	SA, M	—
I10	GPS monitoring and tracking reports	—	M, CRM	—
I11	Sales Manager reports and CRM attendance (web)	—	A, M	—
I12	Remaining CRM items	—	M, E-CRM, CRM	—

I1. CRM masters (Admin): Demo Status, Status Master, Associate Types, Qualifications, Specializations

Steps: create the item (Add icon, enter in field, Submit), set Active or Inactive; duplicates not allowed; update the name with the edit icon then save. To inactivate an item, transfer all employees in that existing item to another one first.
Statuses: Active, Inactive. Notifications / Not documented: Not documented. Screenshot status values: Client Status Interested, Not Interested, Won, Follow-up (plus Lost per the text); Demo Status Call For Demo, Demo Scheduled, Demo Pending, Demo Completed.
Help Center: Help › For Admin › CRM Field force management › 1.1 Demo Status · Help › For Admin › CRM Field force management › 1.2 Status Master · Help › For Admin › CRM Field force management › 1.3.a Associate Type · Help › For Admin › CRM Field force management › 1.3.b Qualifications · Help › For Admin › CRM Field force management › 1.3.c Specializations

I2. CRM leave policies (Admin)

Steps: Super Admin sees the common rules for all leave types; clicks Edit to change; sees default leave types and can Edit them; click Submit to save.
Help Center: Help › For Admin › CRM Field force management › 1.4 Leave Policies

I3. Add client to activity to payment (Sales Executive, web)

Trigger: Employee clicks Add Client on the CRM dashboard.
Actors: Sales Executive / Field executive; Manager (reassignment).
Steps:
1. Enter Organization, Contact Person, Contact Number, Address1, Country, State, City, Description; click Submit (Reset clears). The client displays in Clients List.
2. Client List: two dashboards via dropdown. Client Demo Status columns: Leads, Call for Demo, Demo Pending, Demo Completed, Future Leads. A first-time client displays under Leads.
3. Client Status columns: Interested, Follow-up, Won, Lost, Not Interested.
4. Click the edit icon for a client; click Add Activity; select Activity Type, Follow-up Date, Follow-up Time, Demo Status, Status; enter Description; if Status is "Won", a Final Price field displays; click submit.
5. Activity totals and Payments details display; click Add Payments; select Payment Method, Collected Amount, enter Description; click submit; payments display in the table.
6. The field executive can update the activity type based on the status until the lead gets closed.
Statuses: Demo columns and client status columns above. If the Activity Status is other than CALL FOR DEMO, DEMO PENDING or DEMO COMPLETED, the client moves to "Future Leads". . Lead age colours: green 0-7 days, amber 8-14, red 15 plus. Activity types: VISIT, CALL, MESSAGE, MAIL. Payment methods seen: CASH, CARD. ,
Notifications: Not documented.
Variants: The Add Client button on web is configurable (enabled if the client wants to add client and activity details from web). . Mobile: I8.
Not documented: Lead closure rule, how Won or Lost closes the lead, deletion of clients.
Help Center: 4.2.1 Add Client ↗ · 4.3.a Client Demo Status ↗ · 4.3.b Client Status ↗ · 1.2 Clients ↗ · 4.2 Employee Dashboard ↗

I4. Manager view of clients, reassignment

Steps: Clients display segregated by activity status; click a client to see client and activity details; the manager can add a new activity and assign that activity to another employee if the creating employee is not available; the manager can change assignment if the assigned employee is not available.
Not documented: Notification to the newly assigned employee.
Help Center: 1.2 Clients ↗

I5. Client Associates (mobile)

Steps: Client Associates tab, Add (+) icon; select Associate Type, Qualification, Specialization; enter Name, Contact Number, Email; Save; the associate displays on the front screen.
Variants: Manager: Add, Save, Clear. . Super Admin reports by Associate Type, Qualification, Specialization.
Help Center: 4.5.d Client Associates ↗ · 5.5.d Client Associates ↗ · Help › For Admin › CRM Field force management › 3.1 Client Associate Reports

I6. Client Payments (mobile)

Steps: Client Payments tab, Add (+); select Payment Method; enter Collected Amount and Description; Save.
Variants: Screenshots: read-only Final Price and Pending Amount.
Help Center: 4.5.e Client Payments ↗ · 5.5.e Client Payments ↗

I7. Team Travel Approvals: Pending, Verified, Approved, Claimed

Trigger: An employee has travel records.
Actors: Employee; Manager (verify or reject); Finance Manager (approve).
Steps:
1. Employee: Travel Approvals page with Select Employee (defaults to the logged-in employee), From Date, To Date, Minimum Visits; travel records display in the Pending tab.
2. Manager: Team Travel Approvals with Select Employee (default All Employee), dates (default current date), Minimum Visits (default 0), Search, Clear.
3. Select records; a summary shows in the "Selected Records Summary" table; the manager verifies or rejects.
4. Verified records appear under Verified; records approved by the Finance Manager appear under Approved; rejected by the manager or Finance Manager appear under Rejected.
5. Travel Summary and All tabs show Verified, Approved, Rejected, Claimed.
Statuses: Pending, Verified, Approved, Rejected, Claimed (tabs: Pending, Verified, Approved, Travel Summary, Rejected, All).
Notifications: Not documented.
Variants: Mobile: Reports tab, Travel approvals; select From and To date, Minimum Visits, Search; manager's Team Travel Approvals adds Employee Name and Verify and Reject buttons. . Screenshots: editable "KM Revised" field; travel amount = revised km multiplied by rate. ,
Not documented: The step that moves a record to Claimed, the Finance Manager's approval screen for travel, the rate source, payout.
Help Center: 4.4 Travel Approvals ↗ · 1.9 Team Travel Approvals ↗ · 5.7.b Team Travel Approvals ↗

I8. Mobile CRM daily field flow: punch, client, activity

Steps:
1. Punch In or Out: the camera tab opens Punch In with camera, name and address; click Take Picture, which enables Punch In/Out; the image is captured.
2. Add Client: click the camera to take a picture; enter Organization, Contact Person, Contact Number, Email, Address1, Address2; select Country, State, City, Pin code; enter Expected Price and Description; Save; the client goes to the LEADS column of the Activity dashboard.
3. Add Activity: select Activity Type, Follow Up time, Follow Up Date, Demo Status, Status; enter Final Price and Description; Save. The client moves from Leads to Call for Demo, Demo Pending, Demo Completed and Future Leads depending on the Demo Status.
4. Image-only activity: Activities screen, Add Activity, camera icon, Take Picture, Description, Save.
5. Today's Follow-ups: select date and employee name; search.
6. Client Details: Edit Details, Update (saves) or Cancel.
Variants: The Manager has the same features plus Employee Location. . Screenshots show client location verification icons (matched, not matched, not available; the first visit's location is used when the client has no location).
Help Center: 4.3 Punch In/Punch Out ↗ · 4.4 Add Client ↗ · 4.5.a Add Activity ↗ · 4.2.2 Activities ↗ · 4.2.1 Today's Followup's ↗ · 4.5.c Client Details ↗ …

I9. Device approvals

Trigger: An Employee changes the mobile device; the next login device requires approval from the Manager.
Actors: Manager (Super Admin page has the same text).
Steps: All Device Approvals display under this screen. Approve and reject buttons are Not documented.
Help Center: 1.7 Device Approvals ↗ · 1.6 Device Approvals ↗

I10. GPS monitoring and tracking reports

Steps: Assigned employees' live tracking displays on the dashboard map; the current day by default; past dates selectable; battery percentage visible after the employee punches in and starts tracking; total employees punched in and out for the day display.
Variants: Two GPS modes: Point-to-Point (route built from punch-in, punch-out and visit activities) and GPS Monitoring (continuous movement). Tracking needs login to the CRM app, location permission and internet; the map is Google Maps. . Mobile Manager: Employee Location tab; click the location icon to display present location.
Help Center: 1.1 GPS Monitoring ↗ · 1.6 Employee Activity Report ↗ · 1.8 Employee Tracking Log Report ↗ · 1.10 Assignments Report ↗ · 5.6 Employee Location ↗

I11. Sales Manager reports and CRM attendance (web)

Steps: Attendance Summary Report (First in, Last Out, Total and Productive hours; Excel and PDF; Details hyperlink for break hours); Attendance Detailed Report (month-based absents, presents, late count); Missed Punch Report (Month and Year default present month, Employee Name default All Employees). , ,
Help Center: 1.3 Attendance Summary Report ↗ · 1.4 Attendance Detailed Report ↗ · 1.11 Missed Punch Report ↗ · Help › For Admin › CRM Field force management › 2.1 GPS Monitoring · 1.15 Leave History ↗

I12. Remaining CRM items

Help Center: 1.13 Configure Shift ↗ · 1.12 Leave Approvals ↗ · 2.1 Account Creation ↗ · 2.1 Installation ↗ · 4.2 Employee Dashboard ↗ · Help › Mobile App …

Module: Mobile apps (8 workflows)

ID	Workflow	Actors	Apps	End state
J1	Attendance request (employee) and approval (manager), Spryple HCM	Employee; Manager.	HCM	—
J2	Leave and comp-off (mobile HCM)	—	HCM	—
J3	Mobile payslip view	Employee ("employee is able to check payslip").	HCM	—
J4	Rewards and Recognition (send and receive)	Employee, Manager (both can send and receive).	HCM	—
J5	Mobile HCM manager reports	—	HCM, Lite	—
J6	Spryple Lite: add employee and configure user	Manager; Receptionist; Employee.	Lite	—
J7	Mobile app installation and access	Manager, Employee ("give the necessary credentials based on the role (Manager or Employee)").	HCM, Claims	—
J8	Mobile punch with camera (CRM)	Sales Executive / employee ("employee able to punch in/out"); Manager ("manager able to punch in/out").	CRM	—

J1. Attendance request (employee) and approval (manager), Spryple HCM

Trigger: Employee opens Attendance Management in the dashboard.
Actors: Employee; Manager.
Steps:
1. Employee: login with Company Code, Username, Password; click Attendance Management then Attendance Request.
2. Select Work Type, From Date, To Date, enter reason, click Submit; the message "Attendance Request Applied Successfully" displays.
3. Attendance History shows submitted, approved, rejected requests.
4. Manager: Attendance Management, then Pending Approvals; submitted requests display; click the Submitted button to get Approve and Reject buttons.
5. Approve shows "Attendance Request Approved Successfully" and the status changes to Approved in the employee's login; Reject shows "Attendance Request Rejected Successfully" and the status changes to Rejected.
Statuses: Submitted, Approved, Rejected.
Notifications: On-screen confirmation messages above; push or email Not documented.
Variants: Web equivalent C2 and C4. Screenshots add half-day checkboxes, required Shift, Attendance Type (Full Day).
Not documented: Rejection reason on mobile.
Help Center: Applying Attendance Request by Employee ↗ · Approving Attendance Request by Manager ↗

J2. Leave and comp-off (mobile HCM)

Steps:
1. Leave request (employee): Leave Management, Leave Request; select Leave type, From Date, To Date, enter reason, submit; "Leave Request Submitted Successfully".
2. Leave approval (manager): Leave Management, Pending Approvals; click View; Approve or Reject; "Leave Request Approved Successfully" or "Leave Request Rejected Successfully".
3. Comp-off request (employee): Leave Management, Comp-Off Request; select Worked Date, Worked Hours, Minutes, reason, submit; "Comp-Off Request Submitted Successfully".
4. Comp-off approval (manager): Leave Management, Comp-Off Approvals; View; Approve or Reject with matching messages.
Statuses: submitted, approved, rejected.
Notifications: On-screen messages; others Not documented.
Variants: Web: D5, D6, D9.
Help Center: Applying Leave Request by Employee ↗ · Approving Leave Request by Manager ↗ · Applying Comp-Off Request by Employee ↗ · Approving Comp-Off Request by Manager ↗

J3. Mobile payslip view

Actors: Employee ("employee is able to check payslip").
Steps: Click payroll management; the payslips screen displays; select Financial Year and Month; Net Pay, Total Earnings and Deductions display.
Help Center: Spryple HR ↗ · PAYROLL MANAGEMENT ↗

J4. Rewards and Recognition (send and receive)

Trigger: User clicks Rewards & Recognition in the dashboard.
Actors: Employee, Manager (both can send and receive).
Steps:
1. Click the add button; select the Employee name from the dropdown, the Recognition Type and Message (the message can be edited in the box); click Submit.
2. Data displays in the Sent List; the selected employee sees the message in the Received list.
3. Reports (top right) show the count of Recognition types for each employee.
Variants: Recognition types in screenshots: Birthday, Outstanding, Job Well Done, Congratulations, Performance-based recognition; template message with 145-character limit.
Help Center: Manager & Employee Logins ↗ · REWARDS & RECOGNITION ↗

J5. Mobile HCM manager reports

Steps: Today Attendees (multiple check-ins and check-outs for the current day); Attendance Details (check-ins and check-outs date-wise); Attendance Summary (default current month to date; Present Count per employee; month selectable with the calendar icon). , ,
Help Center: Today Attendees ↗ · Attendance Details ↗ · Attendance Summary ↗ · 4.4 Payroll Reports ↗

J6. Spryple Lite: add employee and configure user

Trigger: Manager logs in to Lite.
Actors: Manager; Receptionist; Employee.
Steps:
1. Add Employee: enter Name, Mobile Number, Monthly Salary, Shift.
2. Configure User: edit the employee and manage facial recognition profiles; status Verified or Not Verified; grant camera permission.
3. Employees self check-in and check-out on their own devices; the Receptionist login lets added employees check in and check out. ,
Statuses: Verified, Not Verified.
Variants: Spryple Lite is listed as unmaintained (last release 2024-08) in a secondary store listing, outside the Help Center.
Help Center: 4.1.1 Add Employee ↗ · 4.1.2 Configure User ↗ · Employee Login ↗ · 4.5 Receptionist Login ↗ · 2.1 Account Creation ↗

J7. Mobile app installation and access

Actors: Manager, Employee ("give the necessary credentials based on the role (Manager or Employee)").
Steps: Open the Play store (HCM, Lite, Claims: search by app name; CRM: Play store or App Store); click Install; accounts are created in the integrated web application; open the app and give the credentials for the role; ensure internet connection. ,
Help Center: 2.3 Usage of App ↗ · 2.3 Usage of App ↗ · 2.1 Installation ↗ · 2.1 Installation ↗

J8. Mobile punch with camera (CRM)

Actors: Sales Executive / employee ("employee able to punch in/out"); Manager ("manager able to punch in/out").
Steps: See I8 step 1.
Help Center: 4.3 Punch In/Punch Out ↗ · 5.3 Punch In/Punch Out ↗

Module: Learning Management System (6 workflows)

ID	Workflow	Actors	Apps	End state
K1	Course builder to course saved (LMS Instructor)	Instructor.	I	Course saved. Course cards in screenshots show modules, sections, duration, "what you will learn", prerequisites, Enroll and Details.
K2	Employee course enrolment, assessment, certificate	Employee.	E	Certificate in My Certificates. Certificate of Completion shows recipient name, course, date, tenant name, instructor signature and a Certificate ID (example `CERT250811174612SELE10`); no score or duration.
K3	Learning Sphere and badges (employee)	—	E	—
K4	Instructor dashboard and reports	—	I	—
K5	Manager and Admin LMS views	—	A, M	—
K6	LMS access note	—	—	—

K1. Course builder to course saved (LMS Instructor)

Trigger: Instructor logs in to the LMS and opens Course Builder.
Actors: Instructor.
Steps:
1. Course Builder shows all courses with an Add Course button.
2. Click Add Course; add Course Title, Tags, Course Description, Difficulty level, Category, Prerequisites, Course Image.
3. Click Next; the Course Content Page displays; add Module, Section and content.
4. Click Next; the Review Page displays; click Submit Course and the course is saved.
Statuses: Not documented. The word "publish" is not used on the Instructor page; the documented end of the flow is "Course will be saved".
Notifications: Not documented.
End state: Course saved. Course cards in screenshots show modules, sections, duration, "what you will learn", prerequisites, Enroll and Details.
Not documented: Publish or unpublish, course assignment to employees (an "Assigned" course tab exists in screenshots ), editing a saved course, assessment authoring (the Employee page shows an assessment; the Instructor page lists no assessment step).
Help Center: Course Builder ↗

K2. Employee course enrolment, assessment, certificate

Trigger: Employee clicks Course Library in the Learning Management System left menu.
Actors: Employee.
Steps:
1. The Course Library page displays all courses and search options.
2. Employees can enroll in the course and complete the course.
3. Click the Assessment icon; the employee Assessment displays; click Submit Test to submit.
4. My Certificates displays the certificates of completed courses; My Badges displays earned badges and Next Targets.
Statuses: Screenshots: assessment result shows correct and wrong counts, score and "Passed".
Notifications: Not documented.
End state: Certificate in My Certificates. Certificate of Completion shows recipient name, course, date, tenant name, instructor signature and a Certificate ID (example CERT250811174612SELE10); no score or duration.
Variants: Screenshots: Course player tabs Content, Summary, Resources, with video player and section progress; assessments are MCQ (A to D) with Mark for Review and a question navigator. Course Library filters: Department, Difficulty (Beginner/Advance), Time, Instructor, Status.
Not documented: Pass mark, retake rules, what triggers certificate issue, approval to enrol.
Help Center: Course Library ↗ · My Certificates ↗

K3. Learning Sphere and badges (employee)

Steps: Learning Sphere displays number of sections completed, Leader Dashboard, Course Information. . My Badges: earned badges and next targets.
Variants: Screenshot menu: Learning Sphere, Course Library, Achievements Center; badge ladder APPRENTICE, SCHOLAR, MENTOR, GUIDE, PATHFINDER, EXPERT by course count.
Help Center: Learning Sphere ↗ · My Badges ↗

K4. Instructor dashboard and reports

Steps: Dashboard displays Courses Overview, Leader Board, Progress, Badges Earned by Category (and one further panel named in the source). Reports displays Employees enrolled, completed, Badges, Points, Certificates count. ,
Help Center: Dashboard ↗ · Reports ↗

K5. Manager and Admin LMS views

Steps: Manager dashboard and Reports have the same contents as K4. , . Admin (HR Manager dashboard) shows the dashboard; Configurations: admin clicks Edit to change the attribute values.
Not documented: Which attributes exist in Configurations, how a Manager assigns courses.
Help Center: Dashboard ↗ · Reports ↗ · Configurations ↗

K6. LMS access note

Module: Administrative master data and policies (14 workflows)

ID	Workflow	Actors	Apps	End state
L1	HR Policies configuration	—	A	—
L2	Onboarding Settings and Offboarding Settings	—	A	—
L3	Work Location	—	A	—
L4	Department and Designation	—	A	—
L5	Holidays	—	A	—
L6	Checklist (onboarding and offboarding masters)	—	A	—
L7	Induction types	—	A	—
L8	Announcements lifecycle (Admin)	Admin; employees (audience).	A, E	—
L9	Company Information and Company Logo	—	A	—
L10	Messages Master (Admin), and other message masters	—	A	—
L11	Overtime duration	—	A	—
L12	Finance Admin setup order in the documentation	—	A	—
L13	Super Admin dashboard	—	SA	—
L14	Main dashboard alerts	—	E	—

L1. HR Policies configuration

Trigger: Admin clicks HR Policies in the Employee Management module.
Steps:
1. Configuration rules for all EMS Types display (48 numbered rules).
2. Rule groups: password rules 1 to 9; onboarding reminders and probation 10 to 12; offboarding reminders and notice period 13 to 15; default week offs 16 to 18; automatic shift assignment 19 to 21, 25, 26; late attendance deduction 22 to 24; half and full day hours 27 and 28 (4 and 8 hours in the text); paid permission 29; flexible shift 30 and 31; regularization 32 and 33; employee details editable 34; default punch out 35; department-designation mapping 36; backdated termination 37; lunch, tea break and grace periods 38 to 42; extra days payment 43 to 45; week-off penalty 46 to 48.
3. Click the save button. For rules 37 to 42 and 48 the text states a check box must be selected for the policy to update; otherwise update policy does not update and an error message displays.
Help Center: HR Policies ↗

L2. Onboarding Settings and Offboarding Settings

Steps: Onboarding Settings: toggle Send Automatic Reminders (if enabled, reminder messages go to employees to complete onboarding pending checklists); toggle Probation Period (if enabled, a Probation Period (In Months) dropdown displays). . Offboarding: see F1.
Not documented: Reminder frequency.
Help Center: Onboarding Settings ↗

L3. Work Location

Steps: Click Add; select current location or search; enter Address1, Address2, Branch Location, Country, State, City, Pin code, Prefix and seed; click Submit; multiple work locations can be added; edit (seed need not be entered when the prefix already exists); view shows disabled fields.
Statuses: Active, Inactive.
Help Center: Work Location ↗

L4. Department and Designation

Steps: Click Add; enter the name; Submit; edit and save; set Active or Inactive; duplicates not allowed. To inactivate, transfer all employees in the existing department or designation to another. ,
Variants: Department Designation Mapping, see B9.
Help Center: Department ↗ · Designation ↗

L5. Holidays

Steps: Click Add; fields Branch Location, Date, Holiday Type dropdown, Holiday Name; Submit; edit, delete; Public and Optional radio buttons filter lists; search branch-wise. Holidays apply to the entire company or specific branches and are considered in leave duration. Duplicate holidays for the same date and branch are not allowed.
Help Center: Holidays ↗

L6. Checklist (onboarding and offboarding masters)

Steps: Click Add; select Onboarding or Offboarding by radio button; select Department; enter the Checklist name; click the add icon; set Active or Inactive; edit and save.
Help Center: Checklist ↗

L7. Induction types

Steps: Click Add to create a new Induction (HR Policies, Domain knowledge etc.); duplicates not allowed; enter the Program type and Submit; edit; set Active or Inactive; save or cancel.
Help Center: Induction ↗

L8. Announcements lifecycle (Admin)

Trigger: Admin clicks Add in Announcements.
Actors: Admin; employees (audience).
Steps:
1. Select Topic from the dropdown; enter Title; select Publish from and Publish To dates; enter the description.
2. Click Submit (status Published) or Save as Draft (status Save as Draft).
3. Actions by status: Published shows edit, view and stop icons; Save as draft shows edit and view; Completed shows View and Republish; Cancelled shows view only.
Statuses: Published, Save as Draft, Completed, Cancelled.
Notifications: Not documented. Company announcements display on the employee main dashboard.
Not documented: Which action moves an announcement to Completed or Cancelled, what Republish does, audience targeting.
Help Center: Announcements ↗ · Login ↗

L9. Company Information and Company Logo

Steps: Company Information: click Edit, enter or update fields, Save, or Cancel. . Logo: Change icon, select image in the file explorer, Open, Save; Cancel discards; Remove deletes the saved image; accepts jpg and png, size up to 1MB; the logo appears before the company name in the header.
Help Center: Company Information ↗ · Company Logo ↗

L10. Messages Master (Admin), and other message masters

Steps: All Error and Success messages are listed with screen names (by default); click Edit, change, click save. . The same pattern exists for Attendance (C20), Leave (D4) and Payroll (E18).
Help Center: Messages Master ↗

L11. Overtime duration

Steps: The user adds the minimum number of work hours per day allowed as per company rules; after submitting shift details, the shift is listed.
Help Center: Overtime duration ↗

L12. Finance Admin setup order in the documentation

Help Center: Finance Admin ↗

L13. Super Admin dashboard

Steps: Login with Company Code, Username, Password; the main dashboard shows Employee Count By Location, Employees By Department By Location, Employee Count (Active, New, Exit), Attendance By Work Type, Employees on Leave by Department, Leaves, Shift Based Headcount by Department, Payroll Amount by Department by Month.
Help Center: Super Admin Dashboard ↗

L14. Main dashboard alerts

Steps: The main-dashboard Alerts panel lists dates with "Attendance not recorded" and quick attendance and leave request actions. . Pending attendance requests appear in the Alerts section.
Help Center: From Main Dashboard ↗

Part 1: App-wise matrix​

Part 2: Workflows per app​

Web: Super Admin (7)​

Web: Admin (58)​

Web: Managers (57)​

Web: Employee (30)​

Web: Employee (Sales CRM) (4)​

Web: LMS Instructor (2)​

Spryple HCM app (16)​

Spryple Lite app (4)​

Spryple CRM app (9)​

Claims (mobile) (2)​

Part 3: Module-wise, step by step​

Module: Access and credentials (6 workflows)​

A1. Login (web, Employee / Super Admin)​

A2. Users Login creation (Admin creates credentials)​

A3. Employee Password Reset (Admin)​

A4. Change Password (Employee)​

A5. Employee profile edit and picture upload​

A6. Employee onboarding checklist view​

Module: Employee management and onboarding (9 workflows)​

B1. New hire to first login (end-to-end)​

B2. Employee Directory maintenance​

B3. Document approval​

B4. Onboarding checklist assignment​

B5. Onboarding checklist completion and No Due​

B6. Induction program (HR manager)​

B7. Employee Reports​

B8. Excel upload of employees​

B9. Employee Department and Designation mapping​

Module: Attendance (21 workflows)​

C1. Biometric ID mapping​

C2. Attendance request by employee (three entry points)​

C3. Attendance request on behalf of employee (Manager)​

C4. Attendance request approval (three ways)​

C5. Shift change request (employee) and approval with swap (manager)​

C6. Permission request (employee) and approval (manager)​

C7. Attendance regularization (employee)​

C8. Manager attendance regularization and approval​

C9. Shift creation and assignment (Admin, Manager)​

C10. Week-off configuration​

C11. Shift rotation: create sequence, assign, reassign​

C12. Excel upload of attendance (Manager)​

C13. Face capture and enrolment (mobile HCM and Lite)​

C14. Receptionist (front office) check-in and check-out​

C15. Geo-location (branch location) configuration​

C16. Extra Days Slab configuration and penalty designations (Admin)​

C17. Extra Days and Penalty Days reports​

C18. Missed Punch report and default punch-out​

C19. Attendance report retrieval (Super Admin, Admin, Manager, Employee)​

C20. Attendance Messages Master (Admin)​

C21. Shift wise report​

Module: Leave (15 workflows)​

D1. Leave policy activation (default leaves)​

D2. Leave policy deactivation​

D3. Common leave rules configuration​

D4. Leave type configuration (per type) and Advanced leave​

D5. Leave request (employee, web)​

D6. Leave approval (Manager)​

D7. Leave cancellation​

D8. Leave request on behalf of employee (Manager)​

D9. Comp-off request (employee) and approval (manager)​

D10. Comp-off request on behalf of employee (Manager)​

D11. Optional holiday request (employee), approval and on-behalf (manager)​

D12. Holiday list and calendar (employee)​

D13. Leave balance and Company Leave Policies (employee view)​

D14. Leave reports (Manager)​

D15. CRM leave request (Sales Executive, web and mobile)​

Module: Payroll (18 workflows)​

E1. EPF configuration​

E2. ESI configuration​

E3. Pay Schedule configuration​

E4. Pay group create, configure, activate​

E5. Assign Pay Group​

E6. Reassign Pay Group (new financial year, increments)​

E7. Monthly payroll generation​

E8. Arrear distribution and history​

E9. TDS distribution​

E10. Variable pay distribution and schedule​

E11. Payroll Policies configuration​