diff --git a/content/actions/reference/encrypted-secrets.md b/content/actions/reference/encrypted-secrets.md
index f7f502c99d00..0d9b03061c29 100644
--- a/content/actions/reference/encrypted-secrets.md
+++ b/content/actions/reference/encrypted-secrets.md
@@ -75,6 +75,12 @@ When generating credentials, we recommend that you grant the minimum permissions
 
 If your repository {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}has environment secrets or {% endif %}can access secrets from the parent organization, then those secrets are also listed on this page.
 
+{% note %}
+
+**Note:** Users with collaborator access can use the REST API to manage secrets for a repository. For more information, see "[{% data variables.product.prodname_actions %} secrets API](/rest/reference/actions#secrets)."
+
+{% endnote %}
+
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
 ### Creating encrypted secrets for an environment
 
diff --git a/data/reusables/github-actions/permissions-statement-secrets-repository.md b/data/reusables/github-actions/permissions-statement-secrets-repository.md
index 0333c71723ba..17aed4665650 100644
--- a/data/reusables/github-actions/permissions-statement-secrets-repository.md
+++ b/data/reusables/github-actions/permissions-statement-secrets-repository.md
@@ -1 +1 @@
-To create secrets for a user account repository, you must be the repository owner. To create secrets for an organization repository, you must have `admin` access.
+To manage secrets using the web interface, you must be the repository owner for a user account repository, or have `admin` access for an organization repository.