That setup would not use the table, ever. You would adjust the lights using the activator device. Bruce does a really nice job of explaining it in this thread. If you want to use the table settings, then you would remove the "activate as group with on command." Essentially, if that setting is enabled, then turning on the activator device just turns the lights on. If it's not enabled, then when you turn the activator device on, the RL instance will apply the table.
Act = will the device be turned on and configured when using the RL table
Off = will the device be turned off when using the RL table
Force = ignore the device's state and send commands anyways. With this turned off, if the RL instance thinks the device is already off, and an off command is sent (like turning off the activator device), then the RL instance will not send the off command (because the device is already off). If this is ticked, it'll send the commands regardless of what state (on/off/color/color temp) the device is in.
The force setting should be fine to leave enabled in most scenarios. It can save on traffic processing/load if you're commanding a large amount of devices. So, say you have 20 bulbs in the RL instance, I would probably uncheck the "force" option (there's other factors that go into this).
