Enable Visibility
Enabling it you can play with all its settings related to the current element.
Disabling it you are sure that all settings will be ignored and all will be displayed as normal. You can reactivate it later and all sub settings will be maintained as you previously prepared.
Always hide this element
Immediately hide the element from the front end. It's useful when:
you want to prepare new page content in more round and publish them only when you are satisfied with the results;
temporary hide an element you will want to reuse later.
Keep HTML
The module by default strip the element HTML tag from the page content. This is useful to create more lightweight pages and prevent unwanted content available to curious users.
But if you really want to maintain the full HTML element in the DOM page you can do it by activating this option.
One purpose is to display it later with a simple JAVASCRIPT removing only the class .dce-visibility-{elementType}-hidden applied to hidden elements.
Display Mode
You can simply hide it or use multiple triggers that will SHOW or HIDE the element based on some conditions.
For example, if you set as to trigger the "Day of the week" with value Monday:
on "Display mode" set to Show the element will be visible only on Monday and be invisible for the rest of the week
on "Display mode" set to Hide the element will be hidden only on Monday and be visible for the rest of the week
Logical Connective
This setting determines how the conditions are combined. If OR is selected the condition is satisfied when at least one condition is satisfied. If AND is selected all conditions must be satisfied.
Debug
Only if you are in developing mode with WP_DEBUG enabled there is also this option that will help you to configure Visibility settings.
If you enable it will display to you:
in the Editor mode will show a panel over the current element with a report of enabling triggers;
in Fronted if you set "Display Mode" on hiding and the element is hidden will display a question mark with the list of triggers that are triggered in that specific context (user, page, time, etc.).
Don't worry if you forget it enabled. When you move the site in production mode (with WP_DEBUG to false) no additional info will be displayed in the frontend.