ASM - Understanding why "Attack Signature Detected" did not block the access

Hmm ... I may have figured it out. Our screen at "Security ›› Application Security : Attack Signatures : Attack Signatures Configuration" appears as follows:

Does that mean that all the signatures not in those two assigned signature sets will not be enforced? And to enforce them immediately (e.g. for the SQL injection set), i move the set to the list and make sure "Block" is checked? I don't want to turn off signature staging (because it would affect new signatures from updates, i would think - for which I DO want a staging interval) - once i've tested, how do I immediately move the newly added signatures from staging to "active"?

thx