Shifts and recorded time
View the published schedule and attendance history. Starting, finishing and breaks are separate actions. If a record is saved but attendance synchronization remains pending, the interface reports that separately.
The employee workspace
Published shifts, time records, assigned tasks, requests, documents and saved pay calculations in one workspace. Employees can see their work and the SABSUS modules available to them without piecing everything together from messages.
Working data requires an account, permissions and relevant connections.
Shifts, tasks and instructions together
Start, break and finish
A request with context, not a lost message
01 / A clear workflow
The company assigns shifts, tasks and materials in the relevant modules. Worker brings the employee's available data and actions into a personal workspace.
Open a published shift, tasks and instructions. Available sections depend on the company, employee profile and permissions.
With attendance configured, choose the location and enter the PIN or QR registration code. Record breaks and the end of work separately.
Read the details, update an assigned task's status and acknowledge an instruction. Acknowledgment is not a knowledge assessment.
Send a manager request with relevant dates, amount or explanation. Review request history and available saved documents.
02 / Working tools
View the published schedule and attendance history. Starting, finishing and breaks are separate actions. If a record is saved but attendance synchronization remains pending, the interface reports that separately.
Open assigned-task details, mark them complete or reopen them within permitted actions. Worker does not replace the full task editor or promise automatic task creation from every message.
Request absence, availability, a shift swap, an advance, expense reimbursement, time correction, a certificate or help. Each request includes relevant information for review. Submission does not mean approval, payout or a changed roster.
Read assigned descriptions, steps and linked materials, then acknowledge them. Personal documents show available text blocks and signer statuses; actual signing takes place through a SABSUS Documents invitation.
Review a saved period calculation: components, deductions, sources, terms and status. Recorded payments and a CSV of the selected calculation are available. Worker displays saved data; it does not calculate, approve or transfer pay.
Use available colleague chats, reply to messages and attach supported files. Voice recording requires microphone permission. Phone, timezone and notification preferences belong to the employee profile.
Requests communicate the situation with context: the absence dates, proposed shift swap or calculation period in question. The decision remains with a responsible person and the appropriate workflow.
03 / Illustrative scenarios
Check the published time, tasks and materials. Complete the configured start registration, then record breaks and the end separately.
Submit availability or an absence request with the relevant dates. Explain the situation and wait for a decision rather than assuming the schedule has already changed.
Open a saved period, inspect its components and terms, and export CSV if needed. Ask the manager a question identifying the relevant calculation.
These are workflow examples, not customer case studies or promised outcomes.
Requirements and boundaries
A SABSUS account, company access and linked employee profile are required. Shifts, tasks, instructions and calculations must already be assigned or saved in the relevant modules. Statistics use loaded records. A PIN or entered QR code is not claimed as GPS, biometrics or proof of physical presence.
FAQ
It shows published shifts and supports relevant requests. Automatic roster generation and approval of changes are not claimed here.
No. It submits a request for review. It is not an approval and does not transfer money.
No. It shows saved calculations, their components and recorded payments. Calculation, approval and actual payout happen separately.
Worker provides available text blocks and signer statuses. Signing requires the appropriate SABSUS Documents invitation.
No. Sections and data depend on company access, the employee profile and permitted modules.
Explore the right workflow, required connections and access boundaries for your scenario.