diff --git a/.github/workflows/community-issue-comment.yml b/.github/workflows/community-issue-comment.yml
index 05ccf99d..139e0f24 100644
--- a/.github/workflows/community-issue-comment.yml
+++ b/.github/workflows/community-issue-comment.yml
@@ -1,6 +1,7 @@
 # This workflow handles issue comments.
+# See for more info: https://github.com/actions/github-script
 
-name: Issue Assignee Comment
+name: Issue Comments
 
 on:
   issues:
@@ -11,8 +12,8 @@ on:
 jobs:
   # When issues are assigned, a comment is posted
   # Tags the assignee with links to helpful resources
-  # See for more info: https://github.com/actions/github-script
   assigned-comment:
+    if: github.event.action == 'assigned'
     runs-on: ubuntu-latest
     steps:
       - name: Post assignee issue comment
@@ -33,3 +34,23 @@ jobs:
               Support Chayn's mission? ⭐ Please star this repo to help us find more contributors like you!
               Learn more about Chayn [here](https://linktr.ee/chayn) and [explore our projects](https://org.chayn.co/projects). 🌸`
               })
+
+  # When issues are labeled as stale, a comment is posted.
+  # Tags the assignee with warning.
+  # Enables manual issue management in addition to community-stale-management.yml
+  stale-label-comment:
+    if: github.event.action == 'labeled' && github.event.label.name == 'stale'
+    runs-on: ubuntu-latest
+    steps:
+      - name: Post stale issue comment
+        id: stale-label-comment
+        uses: actions/github-script@v7
+        with:
+          github-token: ${{secrets.GITHUB_TOKEN}}
+          script: |
+            github.rest.issues.createComment({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: context.payload.issue.number,
+              body: `@${context.payload.issue.assignee.login} As per Chayn policy, after 30 days of inactivity, we will be unassigning this issue. Please comment to stay assigned.`
+            })
diff --git a/CYPRESS.md b/CYPRESS.md
index c582ad7f..207a6c9a 100644
--- a/CYPRESS.md
+++ b/CYPRESS.md
@@ -4,8 +4,10 @@ Currently, integration tests are set up to be run locally with Chrome. When cypr
 
 ## Setup
 
-- First create a local `cypress.env.json` file (this file is in .gitignore and will be ignore by git). Example variables are in `cypress.env.example.json`. You can ask the team for the environment variables to run Cypress tests and paste them into the file.
-- These variables require users to exist in your database that have certain permissions. Firstly you need to create a super admin user in your database.
+First, create a local `cypress.env.json` file (this file is in .gitignore and will be ignore by git). Example variables are in `cypress.env.example.json`. Some of these variables can be configured by following directions in our [Chayn Tech Wiki Guide](https://www.notion.so/chayn/Chayn-Tech-Contributor-Wiki-5356c7118c134863a2e092e9df6cbc34?pvs=4#1e51da106e1a484baf1429a04be71388). The other variables are login credentials for users that must exist in your local database with certain permissions.
+
+To configure the login credential variables in your database, first you need to create a super admin user in your database:
+
 - Create a public user through the UI.
 - In the database in `bloom-backend` you will need to set "isSuperAdmin" column to true for the user you created. See [BLOOM_USERS.md](/BLOOM_USERS.md) for steps on how to set up different users.
 - There are 2 ways of data seeding with users. 1 is via a script in the bloom-scripts repo. Or 2 creating users through the UI (recommended).
diff --git a/README.md b/README.md
index a63e72e0..0c780f78 100644
--- a/README.md
+++ b/README.md
@@ -65,7 +65,7 @@ You will need to run this in the background for the frontend to be functional.
 
 - **For Chayn staff:** You can import all environment variables from Vercel. Please get in touch with the team for environment variables and access to Vercel. If you already have access, you may proceed to the [Vercel Environment Variable Import](#vercel-environment-variable-import) directions.
 
-- **For open-source contributors:** create a `env.local` file and populate it with the variables below. To configure the Firebase variables, [create a Firebase project in the Firebase console](https://firebase.google.com/) (Google account required). Next, obtain the Storyblok token by visiting our [Chayn Tech Wiki Guide](https://www.notion.so/chayn/Tech-volunteer-wiki-5356c7118c134863a2e092e9df6cbc34?pvs=4#84635bd9b82543ccaab4fb932ca35ebf). Note: environment variables provided by Chayn are subject to change at any time, check for updates if you are experiencing problems.
+- **For open-source contributors:** create a `env.local` file and populate it with the variables below. To configure the Firebase variables, [create a Firebase project in the Firebase console](https://firebase.google.com/) (Google account required). Next, obtain the Storyblok token by visiting our [Chayn Tech Wiki Guide](https://www.notion.so/chayn/Chayn-Tech-Contributor-Wiki-5356c7118c134863a2e092e9df6cbc34?pvs=4#bf62b5dcdb43496ea16231ff1815298b). Note: environment variables provided by Chayn are subject to change at any time, check for updates if you are experiencing problems.
 
 ```
 NEXT_PUBLIC_ENV=local