Platform
One platform. Many access worlds.
Q.suite links identities, sites and permissions with different physical access control technologies. Not every system has to be replaced by a new one: existing solutions are integrated wherever suitable interfaces and technical prerequisites are in place.
Architecture
Q.suite forms a higher-level management and permission layer above the connected access systems.
People · Organisation · Sites
↓
Q.suite – management and permission logic
↓
MECHANICAL · OFFLINE · ONLINE · DEPOT · RACK
How Q.suite works
From individual access to higher-level management
The focus is on organisational questions: Which person belongs to which organisation? What role do they have? For which site and which period do they need access? The connected access systems then perform their respective technical function.
The actual transfer of permissions and the available event data depend on the integrated system, the interface and the respective medium.
Identities & permissions
Every permission starts with the identity: people are assigned to their organisation and role and linked to the sites they need access to. This creates a shared view of people, organisational structures and sites – regardless of which connected system technically provides the access.
Module principle
Eight modules. One shared view of all access worlds.

The foundation for all modules. Master data is captured once and available everywhere. Storage and safekeeping locations show at all times where everything is, and every inventory movement is recorded with a receipt. Administrative levels, roles and rights clearly define who sees and edits what.

Rules instead of routine work. Access rights can be bundled into requestable packages, linked to approval levels and mandatory briefings, and assigned automatically based on rules.

Request permissions easily. Employees request the access rights they need themselves, and the responsible departments approve them step by step – without forms or e-mail detours.

Locking systems under control. Mechanical and electronic locking systems are managed centrally with keys, cylinders and locking plan. Every issue, return and reorder is traceable at all times.
Example: dormakaba, ASSA ABLOY (KESO)

Access at distributed sites. Electronic offline components enable digital permission management even where there is no permanent network connection at the access point.
Example: dormakaba skyra, ASSA ABLOY eCLIQ

Assign access rights centrally. Permissions for electronic access control are assigned directly in Q.suite, time-limited and transferred automatically to the access system.
Example: dormakaba exos

Hand over keys traceably. Depot systems support the organised issue and return of physical keys – for example for on-call duty, emergencies or external specialist companies.
Example: LoxTop

Secure server cabinets precisely. Electronic rack locks control who may open which rack in the data centre – person by person instead of with a master key.
Example: TANlock
Frequently asked questions
Does Q.suite replace our existing access systems?
No. Q.suite is designed as a higher-level integration and management platform. Existing systems remain in use wherever they are technically suitable and a supported connection is possible.
Can Q.suite take mechanical locking systems into account?
Depending on the available data and modules, mechanical systems and their media can be included in the management. However, purely mechanical components do not automatically provide information about when a door was actually opened.
Are digital approval workflows already available?
Q.suite follows a process-oriented platform approach. Which workflow functions can already be used in a given project is clarified based on the current product status and your requirements.
What is the next step?
In a personal demonstration, we present the platform and discuss your system landscape. This shows which connections and management processes make sense for your project.
Experience Q.suite live.
In a personal demonstration, we show you how Q.suite fits into your existing access landscape.
