creekpos · SaaS / Online
Employee sign-in and HR workspace · SaaS / Online
This guide uses fictional training data. Available controls depend on your enabled features, plan and permissions.
Prepared against the tested 13 October 2026 build; check your deployed build before following a new control.
Who can use this
Employee / HR staff
Required tools
HR or staff attendance according to role. Requires the appropriate enabled features and entitlement; this guide does not add plan inclusions.
Before you begin
If a control is absent, check role, branch, enabled features and entitlement. If an order or price changed, refresh and review again. Do not repeat an uncertain financial action with a new request.
Steps
- Create the employee and permitted duties as owner/HR administrator. Separate attendance rights from selling, payroll approval and staff-performance access.
- When attendance sign-in is enabled, use the employee’s own session to clock in. Confirm the current shift/attendance state; a shared login cannot establish a reliable individual attendance history.
- Open the authorized HR workspace for attendance, schedules or employee self-service. Employee pay and private staff information stay behind their existing rights and branch scopes.
- Inspect missing punches, exceptions and approved corrections before payroll/reporting. A separate HR hostname needs actual DNS/TLS and deployment; the same credentials do not prove an unconfigured subdomain exists.
Check the result
Review the saved record and its audit/stock/payment state before continuing. A preview, queued request or accepted send is not proof of completed delivery or settlement.
Edition differences and limits
Classic Desktop keeps its native staff, attendance and staff-ledger files. The online HR suite’s scheduling/payroll/employee pages are separate. Do not describe every online HR module as installed in standalone Desktop.