diff --git a/docs/buildsys/koji-cbs-sigs.md b/docs/buildsys/koji-cbs-sigs.md
index 20101de..bc71f03 100644
--- a/docs/buildsys/koji-cbs-sigs.md
+++ b/docs/buildsys/koji-cbs-sigs.md
@@ -5,6 +5,8 @@ CentOS clearly defines what a SIG (Special Interest Group) is : a group of peopl
 Each SIG *must* be approved by the CentOS board, and no action should be taken before that. Once approved and CentOS board meeting minutes published, we can (Infra and Releng) proceed with next steps :
 
 ## SIG onboarding
+
+### Creating SIG authentication Group
 We first need to create the SIG group in IPA (if it doesn't exist yet) and it shouldn't of course conflict with any existing.
 Requirements:
 
@@ -68,6 +70,22 @@ Worth knowing also that in the next minutes, an automatic email alias is created
 Same for SIG members : an email alias following the `<user>@centosproject.org` alias is also created for all SIG members (and pointing to the email address they used when they registered their ACO/FAS account)
 More informations about this in the [Ansible postfix role](https://github.com/CentOS/ansible-role-postfix/blob/master/defaults/main.yml#L71)
 
+
+### Creating SIG namespace on git.centos.org
+
+Each SIG can push to specific branches on git.centos.org (computed automatically from some sig prefixes and sig name).
+To allow a new SIG group to have the automatic right in git.centos.org (and reflect group membership there though centralized authentication), we need to just add `sig-<name>` to the existing `pagure_supported_sigs` ansible list/vars in Ansible inventory.
+
+Once pushed and applied (automatically by Ansible), when a SIG member will login again, his group membership will be synced and such user will be allowed to :
+
+  * push to some specific branches
+  * push to lookaside
+
+More informations about this in the Git section.
+
+
+### Welcome email
+
 While not fully needed, it's now a good idea to send mail to that new SIG to welcome them.
 Something like this :