diff --git a/docs/STEWARDSHIP.md b/docs/STEWARDSHIP.md
new file mode 100644
index 0000000..95fc9ef
--- /dev/null
+++ b/docs/STEWARDSHIP.md
@@ -0,0 +1,35 @@
+_NOTE: This document is, and quite likely will always be, a work in progress. You can, and should, contribute to it to make as useful for GitHub Management Stewards as it can be._
+
+# GitHub Management Steward
+
+`github-mgmt stewards` is a team of people who are responsible for managing the GitHub Management configuration for the organization. They have write access to the GitHub Management repository, can review change requests and merge changes to the `master` branch.
+
+Membership in the `github-mgmt stewards` team should be treated with **exactly as much care as having admin access to the organization**.
+
+## What qualifications are expected from a GitHub Management Steward?
+
+- familiarity with [GitHub Management](ABOUT.md)
+- availability for reviews and merges of GitHub Management configuration changes
+- being a trusted member of the organization
+
+## What is expected from a GitHub Management Steward?
+
+- review and merge changes to the GitHub Management configuration
+
+### How to review and merge a GitHub Management pull request?
+
+- Wait for the `Comment` check to pass
+- Verify that the pull request contains only the changes you expect
+- Verify that the plan posted as a comment introduces **only** the changes you expect
+- Check if there are any open PRs created by the `Sync` workflow (titles starting with `sync`) and merge them first if there are
+- Ask the author of the pull request to provide more context if needed
+- Do **not** update the pull request yourself - let the `Update` workflow do it
+- Merge the pull request if everything checks out and verify that the `Apply` workflow initiated by the merge succeeded
+
+## How to become a GitHub Management Steward?
+
+To become a GitHub Management Steward, you should meet the [qualifications](#what-qualifications-are-expected-from-a-github-management-steward) and ask one of the existing stewards to approve your change request which adds you to the `github-mgmt stewards` team.
+
+## What do I do if...?
+
+GitHub Management is a relatively new project, GitHub APIs are constantly evolving and the GitHub Management configuration is a living document. You will likely encounter situations that are not covered by this document nor [HOWTOs](HOWTOS.md). If you do and you're unsure what to do, please reach out to @testground/ipdx.
diff --git a/github/testground.yml b/github/testground.yml
index db26782..fda99ed 100644
--- a/github/testground.yml
+++ b/github/testground.yml
@@ -33,16 +33,25 @@ repositories:
         - maintainers
     visibility: public
   github-mgmt:
+    # WARN: push+ access here should be treated exactly as cautiosly as org admin role
     branch_protection:
       master: {}
     default_branch: master
     files:
       CODEOWNERS:
-        content: >
-          *       @galargh
+        content: |
+          # The ipdx team is responsible for GitHub Management maintenance
+          * @testground/ipdx
+
+          # The github-mgmt stewards team is responsible for triaging/reviewing configuration change requests
+          # The ipdx team is added here temporarily to witness use patterns in github-mgmt
+          /github/testground.yml @testground/github-mgmt-stewards @testground/ipdx
     teams:
+      # ATTN: do not add teams with push+ access, use github-mgmt stewards team membership instead
       maintain:
-        - w3dt-stewards
+        - ipdx # NOTE: ipdx are the creators of GitHub Management framework
+      push:
+        - github-mgmt stewards
     visibility: public
   infra:
     collaborators:
@@ -218,6 +227,29 @@ teams:
         - StefanGajic
         - StefanMiletich
     privacy: closed
+  github-mgmt stewards:
+    # NOTE: created to capture users with push+ access to github-mgmt repository
+    #  using a team instead of direct collaborators because we want to reference it in the CODEOWNERS file
+    create_default_maintainer: false
+    description: Users that are effectively org admins
+    members:
+      # WARN: membership here should be treated exactly as cautiosly as having an org admin role
+      # ATTN: members are expected to:
+      #  - be familiar with GitHub Management
+      #  - be ready to triage/review org configuration change request in github-mgmt
+      maintainer:
+        - BigLep
+        - galargh
+        - laurentsenta
+    privacy: closed
+  ipdx:
+    create_default_maintainer: false
+    members:
+      maintainer:
+        - galargh
+        - laurentsenta
+    parent_team_id: w3dt-stewards
+    privacy: closed
   maintainers:
     description: Testground maintainers
     members: