Getting Started

What is DSM?
Kuori DSM (Digital Signage Manager) is the web application you use to watch and control a fleet of
Kuori display devices. Every device holds a screen, an SMB control board, and a client that keeps a
connection open to Kuori's servers. DSM is where that connection surfaces as something you can read
and act on.
Three things live in DSM.
Status. Each device checks in continuously. DSM shows which devices are online, which screens
are lit, what their sensors report, and what has gone wrong. When a device drops off or a screen
goes dark, DSM raises an alert.
History. Every check-in, event, and disconnection is stored. You can pull a downtime report for
a week, look at what a single device did last Tuesday, or export the numbers for a service-level
report.
Control. You can rename devices, put them in groups, set their timezone and location, and send
reset commands to the hardware without visiting the site.
What a device is
A device in DSM is one Kuori unit, identified by its Android serial number. Most units also carry a
Kuori serial, which is the number printed on the hardware and the one you will recognise from
delivery paperwork. A unit may drive one or two displays, and DSM tracks each display separately.
Devices do not talk to DSM on demand. They hold an open connection and report on a schedule, so
what you see is the last thing the device said, not a live poll. The Last check-in column tells you
how fresh that is.
Customers and what you can see
Every device belongs to a customer. Your account is granted access to one or more customers, and
you only ever see the devices, groups, alerts, and reports of the customer selected in the top bar.
Switching customer switches everything on the page.
Your role within a customer decides what you can do. A plain user reads. Admins edit devices,
manage groups, and add users. If a button or a tab is missing for you, your role is the reason.
What DSM is not
DSM does not push content to screens. What a display shows comes from the media player behind it,
and DSM's job stops at the hardware. When a screen shows the wrong thing, DSM can tell you the
device is healthy and reset the media player, but the playlist itself lives elsewhere.

Signing in
DSM does not hold your password. Signing in hands you to Kuori auth, the identity service shared by
Kuori's applications, and Kuori auth hands you back once it knows who you are.
The steps
Open DSM. Without an active session the front page shows a Sign in button, in the middle of
the page and at the top right. Both do the same thing.
Click Sign in. Kuori auth opens at once. There is nothing to choose in DSM first.
Sign in with Google, or with a code sent to your email. Both are described below.
You land back in DSM on the Dashboard, or on the page you were trying to reach.
If you open a link to a specific device or report while signed out, DSM skips its front page and
sends you to Kuori auth directly. After you sign in you arrive on that page, not on the Dashboard.
Google first
Use Continue with Google whenever your organisation uses Google accounts. Google holds your
password and any second step your organisation requires, and once you are signed in to Google the
DSM sign-in usually completes without asking you anything. Pick the Google account whose address
your DSM administrator registered. Kuori auth recognises you by that address.
Use the email code when your organisation does not use Google, or when Google is unavailable to
you.
Signing in with an email code
Type your work email address into the Email field and click Sign in.
Kuori auth emails you a six-digit code. The subject is "Your Kuori sign-in code". Give it a
minute before you look in the spam folder. The Resend link on the code screen becomes active
after 60 seconds.
Type the code into the six boxes. The screen moves on by itself after the last digit. Click
Continue if it does not.
The code works once and expires 10 minutes after it was sent. If it has expired, click Resend
and use the newest email. A code you did not ask for can be ignored. Nobody can sign in with it
without also reading your email.
Getting an account
You cannot sign yourself up. Your DSM administrator creates your account first. Until it exists,
signing in fails even with a working Google or Kuori login, because DSM has nothing to attach the
login to.
An account also needs access to at least one customer. An account with no customer access is
refused at login.
Ask your DSM administrator, or Kuori support, to create the account and grant access.
How long a session lasts
A session stays alive for 8 hours of use, and it slides forward every time you do something. Leave
DSM idle for longer than that and the next click sends you through Kuori auth again. If Kuori auth
still remembers you, you are back where you were without seeing a login form. If not, you sign in
as usual. Regardless of activity, no session lives longer than 24 hours from the moment you signed
in.
Access changes take effect immediately. If an administrator revokes your access to a customer, the
next page you open reflects that. You do not need to sign out and back in.
Signing out
Open the account menu at the top right, click Sign out, and confirm. This ends your DSM session
and your Kuori auth session, so the next sign-in asks for credentials again. You land on the DSM
front page.
If you signed in through Google, Google's own session sits above Kuori auth and survives. The next
sign-in still shows you the account chooser, so you can tell which account you are about to use.
No code arrived?
Give it a minute — delivery isn't always instant. If it still hasn't shown up:
Check your spam or junk folder.
Check your trash (deleted items) folder as well. Some mail providers file automated mail there directly, not in spam.
Still nothing? Contact your company's DSM administrator. They can check on DSM's side whether you actually have an account, and set one up or fix it if you don't.
Why the page never says "no account found": For security, the sign-in screen always reports that a code was sent, whether or not an account exists for that email address. This is deliberate — it stops anyone from using the sign-in page to check which email addresses have DSM accounts. So getting the "code sent" message isn't proof you have an account; if no code ever arrives, that's what your administrator is for.
When sign-in fails
DSM shows an error page rather than a blank screen, and the message names the reason. The common
ones are an account that does not exist in DSM yet, an account with no customer access, and a
login attempt that expired because the browser sat on the Kuori auth page too long. The last one
clears itself if you start again from DSM.
A wrong or expired code is reported on the code screen itself. Click Resend for a fresh one.
Repeated wrong attempts lock the account for 10 minutes. That lock lives in Kuori auth, not in DSM,
and it clears on its own.

Navigation
Everything in DSM hangs off one black bar across the top of every page.
Reading left to right, the bar holds the Kuori logo (which returns you to the Dashboard), the page
links, the search box, the customer selector, and your account menu.
The page links
Four links show for everyone.
Dashboard is the fleet summary for the selected customer.
Devices is the full device table.
Groups lists the groups you have defined and lets you open one.
Reports builds downtime reports over a date range.
Admin shows for any administrator and holds user management and customer-wide settings.
If you cannot see a link, your role does not include it. That is the intended behaviour, not a
fault.
The customer selector
The selector in the top bar sets which customer's data every page shows. Devices, groups, alerts,
reports, and search results all follow it.
The selector shows the current customer's name with your role under it. Click it to pick another,
and type in the search box if the list is long. If your account reaches only one customer, DSM
selects it for you and the selector is greyed out, since there is nothing to switch to.
DSM remembers your choice in the browser, so the next visit opens on the same customer.
Before you pick one, pages have nothing to show and say so.
Opening a device or group that belongs to a different customer switches the selector for you, and
DSM tells you it did. Switching customer while a device page is open works the other way round: the
device no longer belongs to the selected customer, so DSM returns you to the Dashboard.
Search
Click the magnifying glass, or press the / key anywhere outside a text field, to open search.
It looks across devices and groups, and across customers too if your account reaches more than one.
Search by device name, serial number, or group name.
The account menu
Your email address at the far right opens the account menu.
It holds a link to your User configuration page, the dark mode switch, and Sign out.
On a phone or a narrow window
Below about 1280 pixels the page links collapse into the account menu, so the same menu carries
both navigation and account items.
Every page works at phone width. Wide tables scroll sideways rather than squeezing their columns.

DSM Client in Android and SMB
DSM Client (Android App)
Runs as an Android application and connects to the SMB via UART or USB, depending on the Android version.
Can be found in the application list or on the Android desktop.
The UI is minimal, showing only status, sensors, and devices as read from the SMB. Scrolling down on the first page reveals the online status and SMB connection status at the bottom.
Kuori DSM Communication Overview
Kuori DSM communicates with devices through a DSM client, which must be installed for DSM to function. The DSM client is an Android application that acts as the communication bridge between the DSM server and the System Management Board (SMB). It collects device data, retrieves status information from the SMB, and securely transmits this information to the DSM.
By default, the client sends a report to the DSM every five minutes, and the DSM pings the client every ten seconds. The DSM client also receives commands from the DSM and forwards them to the SMB or other system components as needed, enabling centralized monitoring, configuration, and remote control of both the display and its connected hardware.
Connection type by Android version:
Android 11 — connects to the SMB via USB
Android 13 — connects to the SMB via UART
The app can be found from android apps, and the UI shows data from latest collection from SMB.
It also shows online status and SMB connection status at the bottom when scrolling
SMB (System Management Board)
System management is handled by the System Management Board (SMB), a microcontroller board connected to all sensors and control systems within the display. The SMB interfaces directly with hardware components and includes configurable relays that can be triggered to power-cycle connected equipment, allowing remote rebooting of external components such as media players, modems, and other peripherals. If a device has an SMB connected, its status can be monitored through the DSM.
The SMB is a circuit board with its own programmable processor, whose firmware—owned and developed by Kuori Oy—can be updated remotely from the DSM by Kuori.
The SMB independently handles all temperature and backlight control. It communicates via serial connection — either UART or USB (serial over USB) — using the Kuori SMB protocol, allowing sensor values, events, and controller states to be read. This data is uploaded to the DSM and can be controlled via the DSM client through the DSM service. The SMB also has 5 relays that can be triggered from the DSM.