Connection log
The System connections log traces every session opened on Swifto: who logged in, from which application (back-office, mobile, POS), when (start and end date), with which version / terminal and from which IP address. A still-open session is highlighted.
Overview
The Connection log is generated automatically by Swifto. Each time a session is opened — a user logging into the back-office, a salesperson starting the mobile application, a POS register authenticating — a row is created, then completed with the logout time when the session closes. Nothing is created manually here: the log is only used to view who was logged in, when, and from which workstation.
Business goal
- Know who was logged in
- Know when (start → end)
- Identify the application and the terminal
- Spot an open or unusual session
Target audience
- Administrators — oversee access
- Management / control — internal audit
- Security / IT — session monitoring
One log among others
This log is part of the Logs module. It is complemented by the Change log (who modified which data) and the Business logs (prices, invoices, sales…).
Access and navigation
Left-hand side menu: Logs → System connections. It is one of the three logs always available (along with the Sales log and the Change log), subject to profile rights.
Visibility conditioned by profile
A user can see their own connections, but access to the connections of all users is reserved for Manager and Administrator profiles. If the entry does not appear in your menu, your profile does not allow you to view it.
List of connections
The page displays the list of sessions, from most recent to oldest. Each row describes a connection: its user, the application used, its start and end times, and the terminal version. A session with no end date (still active) is highlighted.
| User⇅ | Application⇅ | Beginning Date⇅ | Ending date⇅ | Version / Terminal⇅ | IP address | |
|---|---|---|---|---|---|---|
| amine.abdelkefi | Back-Office | 04/06/2026 08:12 | — ongoing — | Web · Chrome 124 | 192.168.1.18 | |
| mouadh.benaziza | Mobile application | 04/06/2026 07:55 | 04/06/2026 12:40 | Android 13 · v3.2.1 | 102.107.135.198 | |
| salma.trabelsi | Back-Office | 04/06/2026 09:03 | 04/06/2026 17:21 | Web · Edge 124 | 192.168.1.31 | |
| caisse_lac2 | POS register | 03/06/2026 18:02 | 03/06/2026 22:15 | POS · v2.7.0 | 192.168.1.50 |
Each column has a quick filter and a sort (⇅ arrows). Sort by User to group all sessions from the same person, or by Start date to see the most recent connections first.
Columns & detail
Table columns
| Column | Description |
|---|---|
| User | Identifier of the account that opened the session. |
| Application | Channel used: back-office, mobile application, POS register… |
| Start date | Exact timestamp of the session opening. |
| End date | Timestamp of the logout. Empty & highlighted = session still active. |
| Version / Terminal | Application version and type of device used for the connection. |
| IP address | Network address of the workstation from which the session was opened. |
The IP: linking the connection to a workstation
The IP address makes it possible to identify the network workstation a session came from — valuable for spotting a connection from an unusual workstation or an unexpected location. It can be used via advanced search.
Sessions & duration
The duration of a session is the gap between the start date and the end date. Swifto displays a total for the period at the top of the list, which adds up the duration of the sessions matching the current filter — useful for measuring presence time on a given channel.
| Session status | Display | Meaning |
|---|---|---|
| Ended | End date filled in | The user logged out; the duration is calculated. |
| Ongoing | End date empty & highlighted | The session is still open (no logout yet). |
A session that stays "ongoing" long after working hours can indicate a workstation left open, or a logout that was not recorded (abrupt browser closure, network loss on the terminal). Cross-check with the user's usual duration.
Applications & terminals
The log distinguishes sessions by access channel. Each channel reports its own application version and terminal type.
Back-Office
Web access from a browser (Chrome, Edge…). Version = that of the browser.
Mobile application
Salespeople / traveling field sellers. Version = that of the Swifto app (e.g. v3.2.1).
POS register
Points of sale. Version = that of the register module (e.g. v2.7.0).
Filter by Application to isolate a channel: for example, show only POS register sessions to check the opening and closing times of points of sale.
Filters & search
The Search button opens a filtering window by period, user and version / application. The quick per-column filters remain available in the table header.
Advanced search
On large volumes, narrow the period first: the display is faster, the duration total more relevant and the export lighter.
Export
The filtered list can be exported for archiving or transmission to an auditor. The export includes the User, Application, Start date, End date and Version / Terminal columns.
PDF export
Printable document of the filtered log, in the chosen language ("PDF English" menu).
Excel export
Rows exported to a spreadsheet for analysis (durations, connection frequency, cross-checks).
The export reflects the current filter. Apply the right period before exporting, otherwise the file will contain all visible sessions.
Rules, roles & permissions
Immutability — the log is read-only: no connection row can be edited or deleted from the interface. This is the condition for its evidentiary value.
Automatic recording — the trace is created by the system when the session opens and completed at logout; the user has nothing to do for it to exist.
Company-level partitioning — you only see the connections of users in your company; sessions from other accounts remain invisible.
Permission matrix
| Action | Operator | Accountant | Manager | Admin |
|---|---|---|---|---|
| View own connections | ✅ | ✅ | ✅ | ✅ |
| Connections of all users | — | — | ✅ | ✅ |
| Filter / search | — | — | ✅ | ✅ |
| Export (PDF / Excel) | — | — | ✅ | ✅ |
| Edit / delete a row | — | — | — | — |
Indicative matrix — actual visibility depends on the profile privileges and the options enabled for your company.
Scenarios & FAQ
Confirming the author of a questionable action
A suspicious change appears in the Change log at 16:45 from IP 102.107.135.198. Cross-check with this log: who had a session open on that workstation at that moment? The author is confirmed with certainty.
Checking a point of sale's hours
Filter Application = POS register and the week's period: the start and end dates give the actual opening and closing times of each register.
A session stays "ongoing" even though the user has left?
The logout was not recorded (abrupt browser closure, network loss on the terminal). The row stays highlighted until the next login / session expiry.
I can't see other people's connections?
Access to the connections of all users is reserved for Manager / Admin profiles. Ask your administrator for the corresponding privilege.
Best practice — monthly access review
Every month, export the log filtered on the period and check for connections outside working hours or from unusual IPs. Archive the file as audit evidence.
