Answer operational questions across customers

Purpose

Let Rhythm staff investigate platform operations across customers while keeping customer record datasets on their separate workspace surface.

How It Works

Rhythm staff open the system query surface for operational investigation. They browse HQ datasets and choose a question about customers, workspaces, jobs, staff or usage. Dataset access remains a separate check from access to the surface. The shared query engine handles descriptions, validation and results. These questions span customers because their subject is the platform’s own records. Workspace datasets remain unavailable on this surface. Staff assistance inside a customer workspace instead uses the security module’s grant process.

Relationships

Cross-customer questions use the same language over system datasets; customer-specific tables have a separate staff-authoring outcome.