From 7c38d0b9cc204e9393f50a858ff3c0e7aac054ae Mon Sep 17 00:00:00 2001
From: Lee Watson <lee.watson@netgo.de>
Date: Thu, 27 Feb 2025 16:16:51 +0000
Subject: [PATCH] clarify instructions for groups

---
 README.md | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index f315272..710febf 100644
--- a/README.md
+++ b/README.md
@@ -31,15 +31,28 @@ Determine the groups to which access is needed, e.g. a specific repository.
 
 If uncertain, ask a Team Member for help!
 
+Technical Instructions - please forgive the complexity
+
 Access for each repo is tracked using the `./groups/` directory; each sub-directory represents a "group" (Note: some "groups" are also "roles", e.g. `admin`)
 
 Most of the groups correspond directly to git repository names, aka "project name"
 
-```bash
+Create a symlink from the group-directory back to the keyfile
+```shell
 cd groups/<project_name>
 ln -s ../../<path_to_key.gpg.pub>
 ```
 
+Example:
+
+Add "Max Musterman" to the group for `devnso-adp-argocd`:
+```shell
+# navigate to group-directory for devnos
+cd groups/devnso-adp-argocd
+# symlink to pubkey for New User
+ln -s ../../max.musterman@netgo.de.gpg.pub
+```
+
 ## 3. Onboarding: [Existing User]: Configure sops config
 
 Context: This repo stores the keys used to encrypt secrets in other repos; these "consumer" repos each contain a sops config `.sops.yaml` which manages access to the encrypted files (e.g. `secrets.yaml`)