Messages and notifications

Daily work

Messages and notifications

SmartLIMS lets you leave messages on a request or on a single sample, and tells you through the notification bell when something concerns you. This page explains both.

Who this is for: Lab staff · You need: the "Manage messages" permission to read and post messages; the notification bell works for everyone

The idea in short

There are two things here:

What it is Where you see it
Messages Notes people write, kept with a request or a sample Activity on the request page, and each sample's own thread
Notifications Your personal list of messages meant for you The bell in the sidebar

Each message is one of two kinds:

  • Conversation: a question or a note.
  • Instruction: something the person working on it must do. Instructions stand out in the thread.

Messages stay with the request or sample they were written on. They can't be edited or deleted, so the thread is also a record of what was said. Messages that SmartLIMS writes itself, such as assignment notices, show System as the author.

Use the notification bell

The bell sits at the bottom of the sidebar, in the Notifications row. On a phone it is at the top, beside your picture. A red number shows how many notifications you haven't read yet. It updates by itself about every 30 seconds.

  1. Click the bell. The Notifications panel opens, newest first. Unread ones have a coloured background.
  2. Click a notification to mark it as read. If it is about a work order or a request, the click also opens it.
  3. Click Mark all as read to clear the whole list at once.

If you have nothing yet, the panel says "No notifications yet."

📷 Screenshot: the open Notifications panel beside the sidebar, with two unread notifications

What you are notified about

Event Who gets the notification
A manager assigns you a line in a work order ("You were assigned to …") The people with lines on that work order
Regulatory limits are seeded, or a regulatory note or legend is edited, on a work order The people with lines on that work order
Someone posts in a sample's thread The sample's assignees (the people configuring it)
Someone posts in a request's Activity The people following the request (Follow a request)
Someone posts a message addressed with To Only the departments and people it is addressed to (Address a message)

You never get a notification for your own message, and taking work yourself (Take, Take group) doesn't send one.

Messages on a sample

Each sample has its own thread, for the people who configure and test it. Use it for anything about that one sample, such as "the second bottle is cracked, use the first". Messages about the whole request belong on the request page.

To open a sample's thread:

  • on the Edit request page, open the sample's ⋯ menu and click Messages; or
  • on the request page, click the red number beside the sample's name. It shows only when the sample has messages you haven't read; the samples list shows the same number.

The Messages panel opens on the right, next to the sample, and shows the thread, oldest at the top and newest at the bottom, with each author, the kind and the time. A New line shows where the messages you hadn't read start. Opening it marks the sample's messages as read.

  1. Type your message in the box at the bottom.
  2. Choose Conversation or Instruction. Point at either one to see what it is for.
  3. Click Post, or press Ctrl + Enter (⌘ + Enter on a Mac).

The sample's assignees get a notification. In the bell it isn't a link yet, so open the request to read it.

📷 Screenshot: a sample's Messages panel with an instruction highlighted in the thread

Messages on a request

Notes about the whole request are under Activity on the request page, at the top right. The number on the button is how many of them you haven't read; opening Activity marks them read.

Activity shows the request's messages and its history together, in the order they happened, oldest at the top: who changed the status and when, who completed a sample's configuration, and what people wrote in between. A New line shows where the messages you hadn't read start. Notices SmartLIMS writes itself show as history, not as someone talking.

  • To see only one kind, click Messages or History at the top. The number beside each says how many there are. All shows both again.
  • The History item in the request's ⋯ menu opens the panel on History.
  • If the request has many messages, click Load earlier at the top to see older ones.

To write a message:

  1. Click Activity.
  2. Type your message in the box at the bottom.
  3. Choose Conversation or Instruction. Point at either one to see what it is for.
  4. To point at a sample or a group of parameters, click the flask button (Reference), search, and pick it. A link is added to your text. In the posted message, clicking the link closes the panel and takes you to that sample, or to that group in its work order.
  5. Click Post, or press Ctrl + Enter (⌘ + Enter on a Mac). If the message can't be posted, the reason shows under the box and your text stays there.

📷 Screenshot: the Activity panel on All, with a status change, an instruction and the New line

Follow a request

People following a request get a notification for each message posted in its Activity. You follow a request on your own when:

  • you are made one of a sample's assignees, or add yourself (Add me); or
  • you take any of its work into work (Take, Take group, Take into work, or taking over a colleague's lines).

Follow at the top right of the request page shows where you stand. Click Follow to follow a request you don't work on, and Following to stop. If you stop and later take more of its work, you follow it again.

The button needs the permission to post messages; without it, it doesn't show.

Address a message to departments or people

Some messages are for a whole department, such as everyone in Reception and in Chromatography, and not for whoever happens to work on the sample. Address those with To:

  1. In the message box, click the people button (To).
  2. Pick one or more departments, people, or both. Type to search. Click again to remove one.
  3. What you picked shows above your text, after To:. Click × on a name to remove it.
  4. Post the message as usual.

Only the people you addressed get a notification: every member of a department you picked and its leader, and the people you picked. The sample's assignees and the request's followers are not notified, unless you picked them. Everyone who can see messages still sees the message in the thread, with → and the names it went to under the author.

Without To, a message notifies as described in What you are notified about.

In a work order's Activity, To starts with the departments of the work order's groups already picked. Remove them if the message is for someone else.

To works in a sample's Messages, in the request's Activity and in the work order's Activity. People who can't see messages are never notified, even when their department is picked.

📷 Screenshot: the message box with To: Reception and Chromatography above the text

Tips

  • Use Instruction sparingly, for things someone must act on. It stands out more when it is rare.
  • Work order notifications go to everyone with a line on that work order, not only to the person just assigned.
  • If you don't see the request's messages or a sample's thread, ask your administrator for the "Manage messages" permission. See Users and roles.
  • Messages stay inside your lab; customers don't see them. Comments exchanged with a laboratory customer through SmartQC are kept separately. See SmartQC.
↑↓ to move ↵ to open esc to close