ores.qt.admin
Table of Contents
Summary
ores.qt.admin is the Qt plugin for identity and access management UI.
It provides MDI windows and dialogs for managing accounts, roles, tenants,
tenant types, system settings, badge definitions, and badge severities.
It also provides the Tenant Onboarding Wizard for provisioning new tenants
and contributes the Configuration and Administration submenus to the System
menu. Variability (feature flags) are surfaced through the system-settings
controllers.
Inputs
- NATS responses from the IAM service (accounts, roles, tenants, tenant types, system settings, badge definitions, badge severities).
- NATS responses from the controller service (variability/system settings).
- User interactions: create/edit/delete/view-history on IAM entities.
Outputs
- Rendered MDI windows for each IAM entity type.
- NATS request messages sent to the IAM and controller services on user actions.
- Configuration and Administration submenus injected into the System menu.
Entry points
include/ores.qt/AdminPlugin.hpp— plugin class; contributes to System menu.include/ores.qt/AccountController.hpp— account entity controller.include/ores.qt/TenantController.hpp— tenant entity controller.include/ores.qt/TenantOnboardingWizard.hpp— multi-step tenant provisioning.
Dependencies
ores.qt.api— IPlugin, base controller/window/dialog classes, ClientManager.ores.iam.api— account, role, tenant, badge domain types and NATS schemas.ores.controller.api— system-setting and variability domain types.ores.variability.api— variability/feature-flag domain types.
See also
- ores.iam.api — domain types and NATS protocol schemas for IAM.
- ores.iam.core — server-side IAM logic and NATS handlers.
- ores.controller.api — system-setting domain types.
- ores.variability.api — variability/feature-flag domain types.
- ores.qt.api — shared Qt infrastructure and base classes.
- Qt Plugin Architecture — plugin lifecycle and menu-contribution model.
- Entity Controller Pattern — controller/window/dialog/model structure.
