A configuration is the policy a conversation is analysed under: a set of operators — each with its own granularity (how often it runs) and context — plus actions that fire when results meet conditions you define. A configuration is addressed by a stable uuid that survives edits, and each response carries a derived sync_state (live or pending) indicating whether the running pipeline reflects the latest change. The Configurations concept guide covers granularity, actions, versioning, and trunk vs per-session use.