diff --git a/github/filecoin-project.yml b/github/filecoin-project.yml
index 671aa26..00cd790 100644
--- a/github/filecoin-project.yml
+++ b/github/filecoin-project.yml
@@ -2256,8 +2256,8 @@ repositories:
     has_discussions: false
     merge_commit_message: PR_TITLE
     merge_commit_title: MERGE_MESSAGE
-    secret_scanning_push_protection: false
-    secret_scanning: false
+    secret_scanning_push_protection: true
+    secret_scanning: true
     squash_merge_commit_message: COMMIT_MESSAGES
     squash_merge_commit_title: COMMIT_OR_PR_TITLE
     teams:
@@ -5206,10 +5206,32 @@ teams:
       # ATTN: members are expected to:
       #  - be familiar with GitHub Management
       #  - be ready to triage/review org configuration change request in github-mgmt
+      # The individuals below are listed as "maintainers" rather than "members" because they are filecoin-project owners/admins.
+      # GitHub will auto-bump their team privileges anyway if we don't manually.
       maintainer:
+        # Why @galargh?
+        # 1. He has deep knowledge of the tool and its use as the creator.
+        # 2. He is co-founder of IPDX, which has a contract in 2024 to support developer productivity in the filecoin-project ecosystem.
         - galargh
+        # Why @jennijuju?
+        # 1. Has a long history with filecoin-project and has a lot of connections to teams across filecoin-project.  
+        #    She often has history or context on projects and can anticipate needs or issues that may arise.
+        - jennijuju
       member:
+        # Why @BigLep?
+        # 1. This can be temporarily, but at least of 2024-08-02, he is a FilOz team member getting github-mgmt setup and operationalized
+        #    (e.g., https://github.com/filecoin-project/community/discussions/710).
+        # 2. He has experience working with github-mgmt in other contexts (e.g., ipfs per https://github.com/ipfs/ipfs/issues/511)
         - BigLep
+        # Whey @rvagg?
+        # 1. He is an active in-the-GitHub-trenches maintainer for FilOz, often touching the 10+ repos that FilOz owns/maintains.
+        #    FilOz wants to ensure changes to these repos is done under code review and transparently,
+        #    and @rvagg is one of the key people who will be reviewing these changes.
+        #    (FilOz is also guinea-pigging this process, but the hope/intent is to have other groups manage their repos in this way too if its successful.
+        #    We are also dependent on some tooling improvement to support a diverse set of stakeholders that have limited blast radius.
+        #    See https://github.com/ipdxco/github-as-code/issues/126 for more info.)
+        # 2. He has experience working with github-mgmt in other contexts (e.g., ipld)
+        - rvagg
   infra:
     members:
       member: