Admin Tip: Using a “Debug” Question to Easily Reveal Hidden Fields in Playbooks

Here’s a helpful trick for Admins who want to test hidden questions in a Playbook.

 Step-by-step: How to set up a Debug toggle

1. Create a new Playbook question

   • Type: Radio Button

   • Name & ID : Debug

   • Answers: Yes / No

   • Default value: No

2. Hide the Debug question for non-admins

   • Add a hiding rule:

     System user role != “Admin”

     This ensures only Admins can see and change the Debug toggle.

3. Make hidden questions controlled by Debug

   Instead of using the rule true to hide questions, update each hidden question’s visibility rule to:

   GQ.Debug = “No”

   This means:

    

   • When Debug = No (the default), the question stays hidden.

   • Admins can switch Debug to Yes to instantly reveal all hidden questions without refreshing data.

Why this is useful?

• You can test hidden logic quickly and smoothly.

• No need to use the Inspector (which refreshes data).

• Only Admins can toggle visibility, keeping the experience clean for regular users.

•  

Let me know if you want an example setup or a quick walkthrough!