I've got a checkbox option 'show feature', that a client can enable or disable. This is an individual setting for each instance.

However, each instance depends on the global settings, which determine WHO sees this feature - 'no-one', 'anyone', 'registered users' or 'admins'.

My concern is that people will tick 'show feature', while having the global setting set to, for example, 'registered users', and then not know why it's not visible for everyone.

My attempt was to do something like this:

[] Show Feature
This setting relies on the global <feature settings>. (link)

or maybe

[] Show Feature
This setting relies on the global <feature settings>. (link)
Feature can currently be seen by *all users*.
Feature can currently be actioned by *admins only*.

But it's so much text that I think users will skip over it.

Another consideration is greying out the checkbox. This could happen when the feature is set to visible for 'none'. But it doesn't solve any problems for other global settings.

  • If changing it has no effect because of a global setting, disable it.
    – Dan Bough
    Dec 11, 2013 at 2:34

1 Answer 1


Either completely hide "[x] Show Features" locally for user roles not permitted of that operation.

if you still need to show it, you can do as illustrated


download bmml source – Wireframes created with Balsamiq Mockups

  • Thanks. I need to show it as it's dependant on a user-set global setting, not a user role. I've gone with something similar to your alternative solution, I'll review it after some feedback and testing.
    – morgoe
    Dec 11, 2013 at 5:45

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.