System

The `/settings` page is the central hub for all organization, access, and integration configuration. It brings together all operational parameters that apply to the entire account into one clear interface with a left sidebar menu.

The larger the system, the more difficult it is to find a specific record in it. Users often remember only a fragment — a piece of a name, half of an order number, an email subject — and need to access that record without first choosing the correct module and applying filters within it. The `/search` module therefore offers a single field into which anything can be entered: the result is a list of records across all main system entities, sorted by relevance. The search is designed to be tolerant of diacritics, capitalization, and minor typos, and to understand context — if the user enters a mathematical...

The `/organisation` page contains complete organization settings divided into several tabs. It focuses on the operational and business profile of the organization — identity, branding, billing information, customer communication, and marketing channels. The overlap with the `/settings` module is intentional; both modules share the same data sections, only in a different arrangement.

Creating a new organization is an action that opens up a completely new workspace in the system — its own customers, products, calendars, settings, and invoicing. The `/new` wizard is therefore intentionally minimalistic: it only asks for what cannot be automatically deduced or filled in later, and leaves everything else to specialized modules, to which the user switches after the first login. The goal is for the first step to be trivial and for decisions like "what color or emoji" not to become an obstacle when creating an account.

No operationally complex system runs flawlessly — integrations fail, users submit incorrectly filled forms, payment gateways occasionally return unexpected error codes. The `/log` module serves to ensure that these events do not disappear over time, but remain traceable, aggregated, and supplemented with context that will enable the problem to be solved. Here, the administrator can quickly find out when and where an error occurred, how often it repeats, and what exactly caused it. The module is intended primarily for technical staff and individuals responsible for operations, but thanks to AI explanations, it is understandable even for non-technical users.

The `/iot` page is the entry point into the world of connected devices in the administration. It is not a standalone operational tool — that would be impractical, because each type of hardware (lock, sensor, gateway) has its own specifics and deserves a dedicated module. Instead, it serves as a guide and educational material: it introduces the concept of IoT in the system, explains how devices are authorized and what they are linked to, and most importantly, links to specialized modules where actual daily management takes place.

Electronic locks are an increasingly common part of modern operations — from hotel receptions through coworking spaces to short-term rentals, where it's not realistic to hand over keys physically. The `/iot-lock` module manages integration with the TTLock cloud and serves as a central control center for all locks in the organization. It allows monitoring whether the lock is available and its battery status, issuing access passwords tied to reservations, remotely opening doors for visitors, and reviewing the history of all events recorded by the lock. This transforms the physical lock into a full-fledged operational tool connected to the rest...

The `/configuration` page is reserved for advanced organization configuration that goes beyond the scope of standard settings available in the `/settings` and `/organisation` modules.

Every organization needs answers to recurring business questions — how much we sold this year, which customers are most valuable, how busy are the reservations, where credit accumulates, which emails are opened. The `/analytics` module centralizes these answers in one place in the form of pre-prepared reports, which are refreshed without user intervention. Instead of manually downloading data from various parts of the system, management, controlling, and operations thus receive a quick overview, which can be shared via a link or exported for further processing. Analytics is available to all roles that have a view on the given topic — business metri...

The `/admin` page is used for **system administration of organizations and their users**. It is primarily intended for internal system administrators who need an overview across all organizations and tools for resolving customer incidents — account blocking, changing organization context, auditing system events.