diff --git a/website/content/docs/configuration/programmatic-management.mdx b/website/content/docs/configuration/programmatic-management.mdx
index a04eb8b14c3e..45f65ac9d355 100644
--- a/website/content/docs/configuration/programmatic-management.mdx
+++ b/website/content/docs/configuration/programmatic-management.mdx
@@ -14,9 +14,7 @@ Use Terraform to manage policies, namespaces, and plugins in Vault.
 
 - **You must have [Terraform installed](/terraform/install)**.
 - **You must have the [Terraform Vault provider](https://registry.terraform.io/providers/hashicorp/vault/latest) configured**.
-- **You must have admin access to your Terraform installation**. If you do not
-  have admin access, you can still generate the relevant configuration files,
-  but you will need to have someone else apply the changes.
+- **You must have sufficient access to run Terraform**. 
 - **You must have a [Vault server running](/vault/tutorials/getting-started/getting-started-dev-server)**.
 
 ## Step 1: Create a resource file for namespaces
@@ -460,4 +458,4 @@ For example, to import the `admin_keys` secret engine from the `admin` namespace
 
 ## Next steps
 
-1. Review the [best practices for programmatic Vault management](/vault/docs/configuration/programmatic-best-practices).
\ No newline at end of file
+1. Review the [best practices for programmatic Vault management](/vault/docs/configuration/programmatic-best-practices).