# Use the built-in UI

> Let SuperDoc render common editor controls while your application owns access, workflow, and storage.



Use the built-in UI when SuperDoc's editing and review controls fit your product. Start with the defaults, then configure
only the surfaces your workflow needs.

## Explore the built-in UI [#explore-the-built-in-ui]

Choose a surface to see where it appears, how it starts, and where to configure it.

> **Interactive map: built-in Editor surfaces**
>
> - **[Toolbar](/editor/built-in-ui/configure-the-toolbar)** — Formatting commands reflect the document, selection, and mode. Controls adapt when space is tight. Initial behavior: React's `SuperDocEditor` creates a toolbar container. A Vanilla integration provides one.
> - **[Comments](/editor/built-in-ui/comments)** — Word comment threads import with the DOCX. People can create, reply to, and resolve them. Initial behavior: The comments UI is enabled by default. In viewing mode, show comments with `viewing.comments: true`.
> - **[Search](/editor/built-in-ui/search-and-replace)** — Find and replace document text, then move between matches across paginated pages. Initial behavior: Off until `ui: { search: true }`. Without it, the browser keeps its native find shortcut.
> - **[Hyperlinks](/editor/built-in-ui/hyperlinks)** — Keep the mode-aware behavior, suppress activation, or render a custom action. Initial behavior: Edit in Editing or Suggesting mode. Navigate in Viewing mode.
> - **[Context menu](/editor/built-in-ui/context-menus)** — Keep the built-in menu, add application actions, or render the complete menu yourself. Initial behavior: SuperDoc shows document-aware actions on right-click.
> - **[Content controls](/editor/built-in-ui/content-controls)** — Show structured fields stored in the DOCX and respond when someone clicks one. Initial behavior: Content-control chrome is enabled by default. Set `ui.contentControls: false` to hide it without removing the fields from the DOCX.
> - **[Ruler](/editor/built-in-ui/ruler)** — Show the active section's horizontal ruler and adjust its left and right page margins. Initial behavior: Off until `ui: { ruler: true }`.
> - **[Responsive layout](/editor/built-in-ui/responsive-layout)** — Fit the document to its container, adapt built-in chrome, and refit after fullscreen changes. Initial behavior: The toolbar responds to viewport width by default. Use `responsiveTo: 'container'` to measure its mount instead.
> - **[Loading](/editor/built-in-ui/loading)** — Keep the built-in progress overlay or let your application own the loading state. Initial behavior: SuperDoc shows document progress until the Editor is ready.
>
> Tracked changes appear as marks in the document. See [Track changes](/editor/track-changes) to review them.


The map groups related surfaces by task rather than listing every implementation component. **Hyperlinks** covers what
happens when a person activates a link. **Context menu** covers right-click actions. **Content controls** covers
structured fields. **Ruler** covers left and right page margins. **Responsive layout** covers zoom and the Editor shell.
**Loading** covers the progress UI shown while a document opens.

## What your application owns [#what-your-application-owns]

The built-in UI does not choose which documents a person can access, authenticate users, save edits, or define your
product workflow. Your application owns those boundaries.

`Config.ui` decides what SuperDoc draws. It does not grant access or enforce permissions.

## Start with the toolbar [#start-with-the-toolbar]

Continue with [Configure the built-in toolbar](/editor/built-in-ui/configure-the-toolbar) to mount it, choose its
controls, and test its responsive behavior.