I have an interface for managing multiple email addresses associated to an account in my web application. This interface is to be used by an administrator.
The interface shows a list of email addresses and provides buttons to delete an email address, make an email address the primary address and mark email addresses as verified. The mark email addresses as verified feature essentially marks the email in the system as confirmed, so the user can start using it. Otherwise, the user would need to click a link sent to that email address to confirm it as theirs.
An email address must be confirmed before it can be made a primary address. So far, I have came up with this interface:
Problem: Because an email can only be made primary once it is verified, the "Make this primary" button would be disabled for row 3 and 5. (Make this primary and mark as verified are mutually exclusive).
Given this, should I just combine those 2 columns into 1?
I think this approach simplifies the interface a fair bit, which is a good thing. The down side is that it is not immediately apparent that you need to mark an email as verified before you can make it primary.
Should I stick with the first interface? Are there better ways to deal with this problem?