Having built a lot of Gerrit systems over the years at various revisions
I can state from experience that there is no special UUID that needs to
exist. This along with the default Administrators group are created
during site initialization through essentially the same processes that
other groups are generated.
For permissions, in your All-Projects repo grant as follows:
Global Capabilities:
Priority: BATCH 'Non-Interactive Users'
Stream Events: ALLOW 'Non-Interactive Users'
After that it's a matter of what other rights you want the group to
have, the current standard on Linux Foundation managed Gerrit instances is:
Global Capabilities:
Email Reviewers: BLOCK 'Non-Interactive Users'
Reference: refs/*
Read: ALLOW 'Non-Interactive Users'
Reference: refs/heads/*
Label Verified: ALLOW -1..+1 'Non-Interactive Users'
Admittedly, the refs/* Read right could probably be removed from our
config as we also allow Anonymous to read, but we generally start with
our Gerrit in a private mode requiring login to be able to see anything.
-Andy-