How do you 'Edit all groups'?

[R.STEED]

How you edit all groups in Instrument edit mode?
After I tick all these articulations, nothing seems to sound differently.
How does it work?

[EvilDragon]

You're not supposed to edit the instrument internally. Just play it. Why would you want to mess with how the instrument was made to be intended?

[R.STEED]

Well why does it give users the option to do so?
There must be a reason for it.
What is the instrument edit mode for?
How do you use it?

[Gregjazz]

There should be an "Edit All Groups" button in the group editor, which will automatically put checkmarks by all the groups for editing. For more information on how Kontakt's instrument editing works, definitely check out Kontakt's own manual, but bear in mind that it's really for creating your own instrument. Orange Tree Samples libraries rely on a lot of scripting, so a lot of these instrument editing controls might not work as expected.

[EvilDragon]

Yep - what Greg said. Instrument edit mode is a part of Kontakt, natively built in. However, with scripted libraries, you REALLY HAVE TO KNOW WHAT YOU'RE DOING. If you don't, just don't touch it. Use the scripted interface and that's it.

[Gregjazz]

I mean, experimentation is totally fine, but realize that due to the scripting, things like ADSRs won't really work as you expect them to. And of course, remember not to save and overwrite the patch.

[whyterabbyt]

Well why does it give users the option to do so?
There must be a reason for it.
What is the instrument edit mode for?
How do you use it?

You're confusing two things; Kontakt (and by extension its User Interface), and the sample-based instrument that is loaded into Kontakt.

The Kontakt User Interface gives people access to Kontakt's underlying functionality so that people using Kontakt can use that underlying functionality to create simple or complex sample-based 'instruments' that are loaded into, and played from within, Kontakt.

However a pre-created sample instrument already has that done. The designer of that pre-created sample instrument has made decisions about how to implement features for the pre-created sample instrument, and will have done so within the framework of functionality that Kontakt provides

Loading a pre-created sample instrument into Kontakt does not 'switch off' the access to Kontakt's underlying functionality, so you will still have access to edit the pre-created sample instrument.
However, changing the settings for that underlying functionality when you dont understand what the sample instrument is doing or how it is doing it, is likely to 'break' the sample instrument, preventing it from working as designed.

Many of the things that are implemented for a pre-created sample instrument in Kontakt rely on Kontakscript to set up complex behaviour.
Kontaktscript is a programming language that lets someone define new behaviours for how the underlying functionality of Kontakt operates in a pre-created sample instrument. Those new behaviours can include replacements for the 'standard' functionality that is accessible via the Kontakt User Interface.

If you go in and change settings for the 'standard' functionality of Kontakt when it is not actually being used by a pre-created sample instrument because that functionality has been replaced by a Kontaktscript, especially when you dont understand what the sample instrument is doing, and how, it is possible that you will have no effect on the instrument, or it is possible that you will 'break' the sample instrument, preventing it from working as designed.

It looks like you've now asked several questions here about changing Kontakt's underlying functionality, seemingly without knowing much about Kontakt, or the specific pre-created sample instrument you are using.
I would suggest tha; you would be far better served learning how to use the specific pre-created sample instrument as it has been designed.