You want an and, not an or.
get ( accountname ) <> "AdminAccount" AND Get(AccountName) <> "user1"
In other words, it doesn't equal one AND ALSO doesn't equal the other,. If it equals either one of them, you want the button.
Every account is going to be unequal to at least one of your options. For example, with an or, "user1" doesn't equal "AdminAccount", so one of your conditions is true, so your "or" is true.
btw If you use "<>" instead of the fancy equals with a slash in it, it's (easily) typable and means the same thing.
Also, it's better to manage these things at the privilege set level, even if it means there's only one user in the priv set. Chances are, another person will come along that needs the same privs, anyhow. Also, you can assign extended privs to priv sets, to take it to an even higher level, as you noted.
Thank you! In my mind, it made no logical sense to use AND. I am still having a little trouble getting my mind around it. It doesn't follow what I would consider to be normal AND behavior. In my mind AND would always fail because it seemed to mean Get(AccountName) would have to be true simultaneously for both accounts...which is not possible since you can only see a given layout as a single user.
But it works now, and I will re-read this a few times to see if I get why.
Thank you! In my mind, it made no logical sense to use AND.
It could also be expressed as:
NOT ( get ( accountname ) = "AdminAccount" OR Get(AccountName) = "user1" )