Service Catalog

Browse production services with owners, tiers, dependencies, runbooks, environments, and health context. This example brings Services and Owners together so engineering teams can find the next task without losing context.

It includes representative records such as identity-api and billing-worker. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Service Catalog
Use this template in Figr

Template facts

Screen

Table

Primary action

Register service

Pattern

Table

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Engineering and security teams need to register service while keeping services, tier 1 and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Services gives users an obvious place to start.
  • Supporting view: Owners keeps the related context close.
  • Primary action: Register service stays visible when people need it.
  • First signal: Services shows a useful value (148).
  • Second signal: Tier 1 gives additional context (23).
  • Sample record: identity-api.
  • Next record: billing-worker.

States worth designing

  • No rows in current filters: say what changed, protect progress, and offer a clear next step.
  • Sorting or bulk action in progress: say what changed, protect progress, and offer a clear next step.
  • Row update conflict: say what changed, protect progress, and offer a clear next step.
  • Bulk update partly failed: say what changed, protect progress, and offer a clear next step.
  • Restricted columns: say what changed, protect progress, and offer a clear next step.
  • Export complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Services → Owners → Register service → Review outcome

Patterns used

Table, Services, Owners, contextual actions, error recovery

Why these choices work

Prioritize columns that help people act. Keep filters when readers drill into details and return; show who owns each unresolved exception.

Pay attention to services and owners. People need to distinguish identity-api from billing-worker. Keep services visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Register service”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Incident Timeline, Infrastructure Overview, Cloud Cost Explorer.

Start from this in Figr

Design a service catalog screen inside our existing product. Use our current components, tokens and content language. Include Services and Owners views, credible records like identity-api, and a clear “Register service” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr