From cdeb77c5d58bb8013c0dde1eb411403819c7eb9f Mon Sep 17 00:00:00 2001 From: Jamil Date: Wed, 24 Apr 2024 12:03:29 -0700 Subject: [PATCH] docs: Fix ambiguity in saas access use case prereqs (#4762) Just a minor wording change. --- website/src/app/kb/use-cases/saas-app-access/readme.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/src/app/kb/use-cases/saas-app-access/readme.mdx b/website/src/app/kb/use-cases/saas-app-access/readme.mdx index eb58d8c7d..2106069e0 100644 --- a/website/src/app/kb/use-cases/saas-app-access/readme.mdx +++ b/website/src/app/kb/use-cases/saas-app-access/readme.mdx @@ -22,8 +22,6 @@ into an **app connector** for SaaS applications that support IP allowlists. ## Prerequisites -- Any SaaS app that supports IP allowlists, configured to allow the public IP - address(es) of the NAT Gateway(s) you deployed above. - A Site with a descriptive name to use for deploying Gateways for this use case, for example `SaaS connectors`. [Create a Site](/kb/deploy/sites) if you haven't already. @@ -33,6 +31,8 @@ into an **app connector** for SaaS applications that support IP allowlists. [Terraform examples](https://www.github.com/firezone/firezone/tree/main/terraform/examples) for examples on how to automate deploying multiple Gateways to various cloud providers. +- Any SaaS app that supports IP allowlists, configured to allow the public IP + address(es) of the Gateway(s) you want to use. For reliable access to your SaaS apps, we always recommend deploying multiple