Team performance

Team performance (Analytics › Team performance) shows, for each person in your organisation, what they did in Linbis — emails, chat, shipments, shipping orders, quotes, warehouse, accounting and every other module — and how long they actively used Linbis, excluding idle time. Every number comes from a record in Linbis. When something cannot be measured, or was not recorded yet, the cell says so instead of showing a zero.

Every employee of your organisation can open the report, and everyone appears in it, including you. It is not the same as the Activity page in the sidebar: Activity is the audit log of individual record changes, while Team performance counts what each person did, and for how long, over a period.

Filters

• Period — Today, 7 days, Month to date, 30 days, or Custom (From / To). A period can be at most 92 days. Days follow your organisation's time zone, not your browser's.
• Division — only the people in one division.
• Shared inbox — narrows the Communication columns to one shared inbox you can open. The other columns are not affected.
• Include @Linbis agents — shows the @Linbis row (on by default).

Updated shows when the numbers were calculated; Refresh recalculates them, at most once a minute. The report has two tabs, Overview and Activity by area; the information icon next to Refresh opens an explanation of how every number is measured.

Overview

• Tiles — Active hours (team), Emails sent, Chat messages, Shipments created, Median first reply and Active today (people with active time today, out of everyone listed). Each tile compares with the previous period of the same length and shows a daily trend. The comparison appears only while the previous period is within the last 100 days; otherwise the tile says No prior period.
• Daily active hours — team — the team's active hours per day, with weekends shaded.
• Where the time goes — the team's active time by area, ranked, with Shipments split by mode and direction.
• Teammates — one row per person. The Column group switch shows Communication, Operations, Records, Time or All, and Columns picks individual columns. Click a column header to sort, search by name, and page through 25 people at a time. The @Linbis row is pinned below the people, and an Unattributed line appears when some emails could not be linked to anyone. Click a row, or press Enter on it, to open that person's page.

Activity by area

A grid of people × areas of Linbis (Inbox, Chat, Shipments, Accounting, …). Measure switches between Time (active hours in each area) and Actions (actions saved from each area). Shipments is split into Air, Ocean and Ground × Export and Import, plus "Shipments · other". Only the areas with activity in the period are shown, with a total row and a total column. The grid spans the full width; select a cell and What they did there opens underneath it, with the option to open that person's log. The grid works fully from the keyboard.

A person whose active time is off, collecting, not tracked, not measurable or not retained shows — here, never 0, and is left out of the totals.

A person's page

Opening a teammate opens a page of their own, at /analytics/team-performance/<user>. The address carries the current filters, so the link can be shared and reopens the same view. The eyebrow above the heading reads Team performance, the heading is the person's name, and Back to the team returns to the table.

The page shows their tiles, Daily active hours by area, Time by area, a comparison Against the team median, Records by module (created, edited, status changes, cancelled, deleted and sent, per module), and What they did: their actions in time order, filterable by module and action. An action that changed a shipment, shipping order or quote expands to show each changed field with its value before and after.

• The log lists every field that changed, including values Linbis recalculates on its own after a save, so it can list more fields than the record's own history tab.
• Related records, such as customers, ports and users, are shown with their current names.
• Money values show as Hidden to people who are not allowed to see financial data.
• Records in private places — emails and chat — are named only to the person who acted; everyone else sees the kind of action without the record. Settings, roles and user administration are never named.

Columns

Every column covers the selected period, and each person is credited only with what they did themselves.

Communication

• Messages sent — emails the person sent from Linbis: replies, forwards, new messages, approved drafts and quote emails. Each email counts once.
• Replies sent — emails sent in a conversation that had already received an incoming email.
• Conversations — distinct email conversations in which the person sent at least one message.
• First reply time — median time from the first incoming email of a conversation to the first reply sent from Linbis, credited to whoever sent it.
• Reply time — median time from an incoming email to the person's next reply in the same conversation.
• Assigned — conversations assigned to the person for the first time during the period.
• Touched — distinct conversations the person opened for the first time, starred, snoozed, marked done, assigned, changed the state of, or replied to.
• Resolved — conversations that are currently Resolved and that the person resolved during the period. Only managers and admins can resolve conversations.
• Chat messages — messages the person wrote in Linbis chat.
• Flag ack time — median time from a red flag being raised in chat to the person acknowledging it.
• Agent-assisted — share of the person's emails that started from a draft prepared by @Linbis.

Operations

• Shipments created, Shipping orders created, Quotes created — records the person created.
• Shipments edited, Shipping orders edited, Quotes edited — distinct records the person changed: any field, the status, or a related record such as charges, containers, parties or legs. A record changed many times counts once, and creating a record does not count as editing it. Documents, and charges not tied to exactly one shipment, are not counted here.
• Quotes sent — quote emails the person sent.
• Status changes — shipment status changes that resulted from the person's actions, however they happened. Saving the same status again does not count; when a change on a master also changes its houses, each shipment counts.
• Milestones logged — tracking events the person entered by hand, such as a pickup or a customs release. Status changes and events Linbis creates on its own are not included.
• Receipts + releases — warehouse receipts and releases the person created.
• Invoices posted — invoices the person posted.
• Documents — documents the person generated.
• Tasks done — CRM tasks completed, credited to the person they are assigned to.

Records

• Records created — records the person created in any module; a bulk action counts every record it created.
• Records edited — distinct records the person changed in any module.
• Actions — the number of actions the person saved. A form saved section by section records one action per section, which is why this can be higher than Records edited.

Time

• Active hours — the person's active time in the period.
• Avg / active day — active hours divided by the days with at least 15 active minutes.
• Days active — days with at least 15 active minutes.
• Top area — the area where the person spent most of their active time.

The @Linbis row counts the work @Linbis agents did on their own: the emails they sent, their replies and conversations, and their first reply time. Its other columns show Not measurable, and it has no active time.

Colours mean the same thing everywhere: each area keeps its colour across the stacked bar, the top area chip and the grid, and each person keeps their avatar colour. A reply-time pill is coloured by comparison with the team median for the selected period — not against a target or an agreed service level.

How active time is measured

• Time is counted in 15-second slots. A slot is active when the Linbis tab is visible at the end of the slot and the person used the keyboard, mouse, scroll or touch in the previous 60 seconds. After 60 seconds without input the time is idle and is not counted.
• Because time is counted in 15-second slots, each switch between active and idle can be off by at most 15 seconds.
• Linbis open in several tabs or on several devices at the same moment counts once. When two areas are active at the same moment, that time is split equally between them.
• If a tab or the browser closes unexpectedly, up to the last minute of active time can be lost.
• Active time is reported by each person's browser. Tampering with one's own browser could only inflate one's own numbers, never anyone else's: Linbis accepts time only for the person who is signed in, and limits how much can be sent and how late.

Turning it on

Active time is measured only after an admin turns it on for the organisation, and for each person only after they have read the notice. Time before that has no data. When that moment falls inside the selected period, the number covers only the part that was measured and is marked incomplete (⚠), with the date measuring started.

An admin turns tracking on in Settings, on the Team performance — Active-time tracking card, which also shows who last changed it and when. Each person then sees a one-time notice that explains what is measured, and measurement starts for them only when they confirm it. The notice is shown again if its wording changes, or if tracking is turned off and on again. Turning tracking off stops the measurement straight away; data already collected is kept until it expires. Every column except the Time columns works whether tracking is on or off.

What is never collected

What people type, what is on their screen, screenshots, page addresses beyond the area of Linbis, page or window titles, and anything done outside the Linbis tab. For active time, the browser sends only the area of Linbis and, for each 15-second slot, whether the tab was visible and whether there was input.

How long data is kept

• Actions and field changes: 100 days.
• Active time: 400 days.
• Older periods show as not retained.

When a cell does not show a plain number

Linbis never shows a made-up zero. When a number is missing or incomplete, the cell says why:

Who gets the credit

• Everything that happens as a direct result of a person's action is credited to that person — for example houses that change together with their master, or values Linbis updates after their save.
• Work that @Linbis agents do on their own goes to the @Linbis row, never to a person.
• Emails sent from Linbis that cannot be linked to a person go to the Unattributed line and count only toward the team total.

Export

Export downloads the teammates table as CSV or Excel (XLSX) with the current filters (up to 92 days). A cell without a plain number is exported with its label, never as 0. You can also export the same table from the Team Performance card on Reports. Every export is recorded in the audit log.