I have an interface that looks like this:

enter image description here

The top three fields (Friendly name, Unique TrackerID and URL Endpoint) all need to be saved for the changes to apply and can be discarded by clicking "Go back and discard changes".

However, the bottom three links (Archive link, temporarily disable link and reset all clicks) all take effect the moment the user clicks them. How do I explain that "Go back and discard changes" will not discard those changes? The way I currently do it is by having the text change when the user clicks them:

enter image description here

However I feel this could still be confusing.

  • 8
    Completely off topic: you'll want to remove the typo from your UI: "permanent" ends in "ent".
    – JeromeR
    Commented Nov 30, 2015 at 18:27
  • 12
    It is confusing because actions look visually similar to settings. Back in my day, actions were triggered by things that looked like buttons. Commented Nov 30, 2015 at 23:32
  • I don't find it confusing, because the settings that need to be saved look like text entry fields, and the ones that take effect immediately look like hyperlinks. Commented Dec 1, 2015 at 0:32
  • 1
    @DanHenderson And hyperlinks look like they perform GET requests and consequently "by law" :-) don't do anything. I had to read the question quite carefully to even understand it.
    – Odalrick
    Commented Dec 1, 2015 at 14:12

3 Answers 3



Name: Sch


Url Endpoint: < removed >

[Cancel changes] [Save information]


[Temporarily disable link]

[Archive link]

[Reset link]

[Delete link]

  • 9
    I'd even rename [Settings] to [Actions]. Actions are active, settings are passive. The first fields actually look like settings; [information] suggests that these are read-only.
    – MSalters
    Commented Dec 1, 2015 at 11:59
  • 1
    Also consider styling your action links/buttons so that they match or are similar to your Save link/button. Commented Dec 1, 2015 at 13:17
  • 1
    @user568458 yeah that's what I tried to indicate. Regular text is text, italics are editable fields, brackets are [buttons]. Commented Dec 1, 2015 at 22:10

Separate the settings that can be changed directly from those that need to be saved. Create an "Additional Settings" option, and place it above the settings that can change directly. When the user clicks on the additional settings, a new screen will appear, displaying the three fields that need to be saved.


You don’t, you fix your UI!

I would make the fields for setting that need to be confirmed read-only and put them inside of a box. At the bottom of the box put an “edit” button. When the edit button is pressed show a popup that allows them to be changed, with “OK” and “Cancel” on it.

Then the current “page”/”dialog”/”whatever” just shows information and has a set of buttons for actions.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.