Overview

Overview

On this page

WorkSmartHub is a work management platform. Companies use it to record and follow jobs (repairs, maintenance, installations, quotes, deliveries) as work tickets, to keep their client and stock records in one place, and to keep every team's work separate from the others.

What it solves#

  • Separate teams, separate data. Each team, department or project gets a workspace with its own access rules, notification channels and file storages. Team members see only what they need.
  • Work tickets without paperwork. A ticket holds everything about a job: the client, the product, the problem, the status, the people assigned, the components used, the work done, the delivery and the attachments. Status changes and assignment changes are sent to the people concerned automatically.
  • Client management. Clients are recorded once and selected on tickets. The client receives an automatic e-mail when a ticket is registered, when a delay is reported and while the job is being delivered.
  • Stock management. The warehouse (Raktárkészlet) keeps the components with quantities and prices. Components used on a ticket are taken from stock, and users responsible for stock get an e-mail when a component runs low.

Architecture#

WorkSmartHub is one web application: an ASP.NET Core server (.NET 10) that also serves the Angular web portal on the same address and port. It runs on your own infrastructure:

  • on Windows under IIS, on Linux as a systemd service behind nginx, in a Docker container, or on Kubernetes with the Helm chart (Installation);
  • with an internal database of your choice: SQLite (default, single server), Microsoft SQL Server, PostgreSQL or MySQL;
  • with users from its own user store or from Active Directory, LDAP, Microsoft Entra ID, or an OAuth provider (Authentication).

Background jobs (reminders, low-stock e-mails, token and password expiry warnings, invoice status sync, database housekeeping) run inside the application process. A REST API with Swagger documentation is available for integrations; it is called with personal access tokens.

One application serves the portal, the API and the background jobs, with your database, cache, file storages and optional external services.

Core concepts#

Concept Hungarian label Meaning
Workspace Munkaterület A separated area for one team. Tickets, workspace notification channels and workspace file storages belong to a workspace. See Workspaces.
Work ticket Munkajegy One job, with client, product, status, assignees, costs and attachments. See Work tickets.
Client Ügyfél The customer of a ticket. Shared by all workspaces. See Clients.
Manufacturer, product group, product type Gyártó, termékcsoport, termék típus The product the ticket is about, in three levels. See Manufacturers and ticket options.
Guarantor Garanciát viselő Who bears the cost (for example the manufacturer's warranty, an insurer, or the client).
Ticket type, work type Munkajegy típus, Munka típus What kind of ticket it is (for example inspection, repair) and what kind of work (for example warranty repair). Work types carry legal text for printouts.
Acting work Munkafolyamat A work step with a default price, added to tickets. See Acting works and deliveries.
Component Komponens A stock item with quantity and price, added to tickets. See Warehouse.
Delivery Szállítás A delivery route with a price, added to tickets.
Notification channel Értesítési csatorna An e-mail, Slack or Microsoft Teams connection used to notify users. See Notifications.
File storage Fájltároló Where attachments and images are stored: server disk, Azure Blob, Amazon S3, MinIO, Box, SharePoint or Google Cloud Storage. See File storages.

Notification channels and file storages exist on two levels: workspace level (used only by that workspace) and application level (App Értesítési Csatornák, App Fájltárolók, usable by every workspace).

Master data is shared by all workspaces; tickets, workspace channels and storages belong to one workspace.

Who uses WorkSmartHub#

  • Application administrators (Super Admin). They install and configure the application, manage users, workspaces and global settings. Usually only a few people.
  • Workspace administrators. They are responsible for one team's workspace: its members, permissions, notification channels and file storages, and all of its tickets.
  • Ticket administrators. They create, edit and delete tickets in their workspace.
  • Technicians (ticket employees). They see only the tickets assigned to them or to their group, and can change a limited set of fields (status, assignees, acting works, components, attachments). The server enforces this on every request.
  • Readers. Users with read permissions see tickets or other resources without changing them.
  • Master data maintainers. Separate application permissions let some users manage clients, manufacturers, components, acting works or deliveries without being administrators.

The details are on Permissions and roles.

How it works#

  1. An application administrator creates the workspaces and gives users and groups permissions in them.
  2. Master data is recorded: company details, manufacturers and product types, guarantors, ticket and work types, acting works, deliveries, components and clients. Tickets can also create a new client on the fly.
  3. Ticket administrators create tickets in their workspace, assign users or groups, choose a notification channel and a file storage.
  4. Assignees work on the ticket: they change its status, add work steps and components, upload attachments. Every change is recorded in the audit log, and status or assignment changes are notified through the ticket's notification channels.
  5. A background job reminds the assignees and the workspace administrators when an open ticket has not changed for a configurable number of days (5 by default).
  6. When the job is done, the ticket can be printed (summary and intake acknowledgement), and, if Számlázz.hu invoicing is turned on, invoiced.

Enterprise features#

  • Authentication and authorisation through your identity provider (Active Directory, LDAP, Microsoft Entra ID, OAuth: Okta, Google, Microsoft or a custom provider), with group-based permissions.
  • Multi-tenancy inside one installation: workspaces are fully separated.
  • Audit: every user action is recorded on the Események (Events) page, errors on the Hiba Események (Error events) page.
  • Several notification channels: e-mail, Slack and Microsoft Teams.
  • Several file storage services: server disk, Azure Blob, Amazon S3, MinIO, Box, SharePoint, Google Cloud Storage.
  • Several internal databases: SQLite, SQL Server, PostgreSQL, MySQL.
  • Personal access tokens for API automation, as an access token and refresh token pair. Tokens work only for API calls, never for browser sign-in, and a revoked token stops working on every server within about a minute.
  • Multi-node operation with a shared database and cache; scheduled jobs run once per occurrence across all nodes (Running in production).

Built-in documentation#

The application has its own short documentation in Hungarian: Bevezetés (Introduction) and Kezdő Lépések (Getting started), both downloadable with Dokumentum letöltése. This wiki covers the same topics in more detail.

The menu#

The left menu shows only the pages the signed-in user may open. With all permissions it looks like this:

Menu section Items
(top) Bevezetés (Introduction), Kezdő Lépések (Getting started), Mobil Alkalmazás (Mobile app, if licensed)
Ügyfélmenedzsment (Client management) Ügyfelek (Clients), Számlák (Invoices, when Számlázz.hu is on)
Gyártók & Típusok (Manufacturers & types) Gyártók & Típusok
Adminisztráció (Administration) Munkaterületek (Workspaces), Munkajegyek (Work tickets), Értesítési Csatornák (Notification channels), Fájltárolók (File storages)
Munkajegy Konfigurációk (Ticket configuration) Garanciát Viselők (Guarantors), Munkajegy Típusok (Ticket types), Munka Típusok (Work types)
Munkafolyamatok Munkafolyamatok (Acting works)
Szállítások Szállítások (Deliveries)
Raktárkészlet (Warehouse) Komponensek (Components)
Szolgáltatás felhasználói katalógus Szolgáltatás felhasználói katalógus (Service user catalog)
Hozzáférési Token (Access tokens) Személyes Hozzáférési Tokenek (Personal access tokens), Admin Token Menedzsment (Token administration)
Felhasználók & Csoportok Felhasználók (Users), Csoportok (Groups)
Külső Felhasználók & Csoportok Külső Felhasználók (External users), Külső Csoportok (External groups)
Profilok Profilok (Profiles, only with a non-local user store)
Alkalmazás (Application) App Konfiguráció, Státusz, App Értesítési Csatornák, App Fájltárolók, Licenc
Események & Naplófájlok (Events & log files) Események (Events), Hiba Események (Error events), Naplófájlok (Log files), Ügyfél Email Események (Client e-mail events)
Fiók (Account) Profil, Jelszóváltoztatás (Change password), Kijelentkezés (Sign out)
A Super Admin sees every menu item. On the right: the ticket editor.
Did not find what you need?

Write to us or book a call. We answer questions about features, installation and licensing.

Contact us