From ac9bc5ad1fb2af181f97ce491ef7ec5546c78b41 Mon Sep 17 00:00:00 2001
From: Jo Humphrey <31373245+jamdelion@users.noreply.github.com>
Date: Thu, 24 Oct 2024 11:38:56 +0100
Subject: [PATCH] Update add-team-secret doc with info about staging sync

---
 doc/how-to/how-to-add-a-team-secret.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/doc/how-to/how-to-add-a-team-secret.md b/doc/how-to/how-to-add-a-team-secret.md
index a1cc1bfaf1..c625d2e5bf 100644
--- a/doc/how-to/how-to-add-a-team-secret.md
+++ b/doc/how-to/how-to-add-a-team-secret.md
@@ -25,6 +25,8 @@ This guide will demonstrate how to -
 2. In the `team_integrations` table, find the row for the relevant team and paste the encrypted secret into the correct field (e.g. `production_govpay_secret`). 
 3. Press save!
 
+Note: If updating a `staging` secret, you can manually kick off the `sync-staging-db` [GitHub action](https://github.com/theopensystemslab/planx-new/actions/workflows/sync-staging-db.yml) outside of its nightly run, to ensure the secret is available on the staging environment sooner.
+
 ### Test
 
 You should now prompt the team representative (e.g. council officer) to test that the secret has been successfully updated, e.g. test a flow with GovPay.