Reports
Audit User Login Activity by Outlet and Device
Activity Status is a login-event audit trail, not proof of employee presence or misconduct. Use it to investigate access patterns while protecting IP address and device information as sensitive operational data.
- Menu path
- Reports -> People -> User -> Activity Status
- Verified from
- Posnic demo and current POS source reviewed on 2026-09-08
Technical source evidence
demo.posnic.io Reports -> People -> User -> Activity Status captured 2026-09-11, frontend/modules/userReport.html Activity Status tab table pagination and export, frontend/static/script/js/modules/js/report_users.js userstatusreportTable and userstatusreportexport, api/src/controllers/users.controller.js userstatusReportTable filters and Report Read permission, api/src/models/user.model.js userstatusReportPage staff_activities query and newest-first sorting
Run the Activity Audit
- Open Reports -> People -> User.
- Choose Activity Status.
- Open Filter and select the required date range and branches.
- Optionally select one user for a focused investigation.
- Apply the filter and review the newest events first.
- Use the page-size control and pagination, or export all matching events to CSV.
Interpret Each Field
| Field | Meaning | Do not assume |
|---|---|---|
| Name | User account attached to the login event. | It does not prove which person had the credentials. |
| Login Date/Time | Formatted event timestamp in the report. | It is not a clock-in or shift duration. |
| Outlet | Branch attached to the activity record. | It does not prove physical presence at that outlet. |
| IP Address | Network address recorded for the event. | Shared networks, proxies and mobile routes can produce repeated or changing values. |
| Device Type | Detected device class. | Detection can be broad or imperfect. |
| OS | Detected operating system. | It is not a managed-device identity. |
| Browser | Detected browser family. | It is not a unique browser installation. |
Investigate an Unexpected Login
- Preserve the report scope and export before records change.
- Confirm whether the employee or manager recognizes the time and outlet.
- Compare nearby sale activity, register sessions and staff roster records.
- Check whether the IP belongs to a shared shop network or expected service route.
- If access is genuinely suspicious, disable or secure the user account and change credentials through the approved process.
- Record who reviewed the event and the resulting action.
Export and Privacy
- Export All To CSV requests all matching events and creates user-status-reports.
- CSV fields are UserName, Date, IpAddress, Device, Os and Browser; the on-screen Outlet column is not included by the current CSV mapping.
- Grant Report Read access only to roles that need this audit data.
- Store exports in an access-controlled location and delete them according to the business retention policy.
- Do not publish screenshots or exports containing real employee names and IP addresses.
Troubleshooting
| Problem | Check | Action |
|---|---|---|
| Expected login is absent | Date, branch, selected user and whether a login event was recorded | Widen the correct scope and verify the account. |
| Many rows share one IP | Shared outlet network or proxy | Correlate with time, user and register evidence. |
| Outlet missing from CSV | Current export mapping | Retain the on-screen scope separately; do not add an invented field. |
| Device or browser seems wrong | User-agent detection limits | Treat it as a clue, not identity proof. |
| Activity is visible to the wrong role | Report Read permission | Review employee role and permission assignments immediately. |