TG
Couchbase Capella · Observability

Alert Management across Three-Level Inheritance

Designing platform-wide alert governance across Organization, Project, and Cluster scopes for nine distinct RBAC roles.

Product Designer Couchbase Phase 1 in engineering build
Platform
Couchbase Capella
Role
Sole Product Designer
Scope
3 Levels · 9 RBAC Roles
Status
In Engineering Build
TL;DR
The Problem
Enterprise teams managing dozens of database clusters lacked a centralized alerting policy. Operators either had to configure every cluster by hand, or suffered from alert noise and untracked override mutations.
The Model
Modelled a strict inheritance hierarchy: Organization → Project → Cluster, governed by the principle: "Most specific level wins", with complete role isolation across 9 RBAC permission sets.
Key Catch
Uncovered an override contradiction during conceptual modelling that would have caused silent alerting failure and forced a costly engineering rebuild before any code was written.
9RBAC roles integrated cleanly
3 → 1levels of inheritance resolution
0breaking rebuilds in engineering
01 / Foundation

The model before the UI.

The hardest problems in enterprise observability are won or lost at the conceptual model level, not on the screen. On Capella Alerting, that meant defining how inheritance resolves across three organizational tiers before opening Figma:

  • Organization: Global baseline alerts set by Organization Admins (e.g. storage exhaustion, cluster unavailability).
  • Project: Optional grouping defaults customized by Project Managers for specific development environments.
  • Cluster: Granular, node-level overrides set by Database Admins for high-throughput production clusters.
"Align on how the system thinks first; the screens will stay simple."
02 / Interactive Prototype

Test the inheritance rule live.

Try switching thresholds at each level below to see how the cluster's effective alerting behavior is calculated in real time:

1. Organization Alert on · every 30 min
2. Project Inherits from above
3. Cluster Inherits from above
Loading effective state...
03 / Edge Cases

The open Reset question.

When an operator overrides an alert threshold at the cluster level, what happens when they want to return to defaults? We surfaced this fork early between product and design:

Passive log. The Overrides view stays a truthful, observational record: it shows what's overridden where, and never mutates state. This is what my design manager and I aligned on, and the rationale held when our skip-level reviewer probed it.
04 / RBAC Architecture

Scoping across nine roles.

Couchbase Capella defines nine RBAC roles ranging from Org Admin to Project Member and Read-Only SRE. The alerting UI dynamically respects permission boundaries: a Project Manager sees who has overridden a cluster alert, but cannot mutate an Organization-mandated security threshold without Org Admin privilege.

05 / Delivery

Outcome & Engineering Build.

By delivering interactive prototypes with clear role matrices and failure states, the design went into engineering build with zero architectural reversals and reduced handoff rework by more than 60%.