DocsUser Interface Guide

User Interface Guide

The User Interface Guide explains the shared navigation, search, tables, modals, status language, and asynchronous feedback used throughout SDM.

Where to find it: Documentation > DNS Manager > User Interface Guide; the described controls appear across the panel.

Available to: All authenticated roles, limited to pages and actions available to their account.

What this page does

This page teaches the common interaction pattern once so each feature guide can focus on its real work. SDM often loads or mutates data without a full page refresh; the button state, toast, table row, and follow-up read together describe the outcome.

Before you start

Use a supported desktop or mobile browser, allow the panel's own JavaScript, and sign in with a named account. If a page is absent from search and sidebar, verify the role before assuming the interface failed.

Shared interface patterns

  • Sidebar and header search: find modules available to the current role; they do not search DNS record contents.
  • Tables: use search, filters, page length, and column actions. Reset filters before concluding that a resource is missing.
  • Refresh: rereads state. It normally does not perform a mutation.
  • Modals: collect fields and confirmations while keeping the parent page visible. Read the confirmation text, especially for provider deletion, DNSSEC, cluster, restore, and user actions.
  • Toasts and inline status: report immediate success or failure. Verify the owning row or status page afterward.
  • Badges: summarize state such as active, pending, stale, disabled, mismatch, healthy, or error; hover/help text and the detail view explain why.
  • Theme: changes presentation only. If a DNS record changes when you switch theme, that would be a much more interesting bug.

How to use it

  1. Open the owning module from navigation.
  2. Clear or set filters deliberately.
  3. Read the current state and open the row action or modal.
  4. Complete required fields and review any destructive confirmation.
  5. Wait for the request to finish, read the returned message, and refresh the resource.

Result and next check

You can distinguish navigation, filtering, state refresh, mutation, and confirmation controls. Continue with the feature page for field-specific rules and verification.

Theme color