A settings page lets admins manage how a workspace is named, accessed and run. Our examples include a settings sub-navigation, fields for workspace name, URL, language and time zone, permission toggles and a danger zone, designed for web and mobile in eight visual styles, each with light and dark themes. Every example is an original design that comes with its HTML code and a DESIGN.md of colour, type and spacing tokens, in light and dark. Free to use and adapt.
16 examples
Upgrade a plan · Cancel a subscription · Invite a teammate · Delete a workspace
Toggles and simple choices can save instantly with a brief confirmation, which feels responsive. Forms with several related text fields usually need an explicit Save button so people can review changes together. Whichever you choose, apply it consistently and warn before leaving with unsaved edits.
Organise by the user's goals rather than your internal architecture, using sections such as General, Members, Notifications, Security and Billing. Keep the most frequently changed settings near the top. A search box helps once a product has dozens of options.
Actions that are destructive or hard to undo, such as deleting a workspace, transferring ownership or resetting data. Separate them visually, explain the consequences plainly and ask for confirmation, often by typing the workspace name, before the action runs.
App screens
UI components
Website sections
Website templates
search_ui_screens (e.g. “billing settings, editorial style”), get_ui_flow for a whole journey, and get_ui_screen_code to pull the HTML and DESIGN.md straight into your project.