#Administration

The back office groups capabilities by operational area. What a user can see and change depends on both active modules and ACL permissions.

#Modules

Runtime modules are enabled per tenant. Dependencies are resolved automatically, while inactive modules do not contribute routes, menus, search sources, or MCP tools.

#Roles and permissions

Assign permissions through roles and direct grants. External APIs that change tenant data require a token associated with an active user and the route permission declared by the module.

#Settings

Prefer database-backed settings panels for runtime behavior. Tenant JSON is reserved for bootstrap values that must exist before the settings database is available.

#Operations

Use the read-only topology command described in Queue operations before starting or changing workers.