Certificate Management

Manage TLS certificates, domains, issuers, environments, expiry dates, renewals, and ownership across services. This example brings Certificates and Domains together so engineering teams can find the next task without losing context.

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

Certificate Management
Use this template in Figr

Template facts

Screen

Table

Primary action

Add certificate

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 add certificate while keeping certificates, expiring soon and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Certificates gives users an obvious place to start.
  • Supporting view: Domains keeps the related context close.
  • Primary action: Add certificate stays visible when people need it.
  • First signal: Certificates shows a useful value (96).
  • Second signal: Expiring soon gives additional context (8).
  • Sample record: api.figr.design.
  • Next record: app.figr.design.

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

Certificates → Domains → Add certificate → Review outcome

Patterns used

Table, Certificates, Domains, 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 certificates and domains. People need to distinguish api.figr.design from app.figr.design. Keep certificates 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 “Add certificate”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Job Scheduler, Environment Configuration, Queue Monitor.

Start from this in Figr

Design a certificate management screen inside our existing product. Use our current components, tokens and content language. Include Certificates and Domains views, credible records like api.figr.design, and a clear “Add certificate” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr