Merge pull request #2541 from port-labs/PORTN-2959-change-support-getport-io-to-support-port-io

sivanel97 · web-flow · commit c3771764876b · 2025-07-13T13:40:16.000+03:00
changed support@getport.io to support.port.io
diff --git a/archive/git-provider/github-exporter/self-hosted-installation.md b/archive/git-provider/github-exporter/self-hosted-installation.md
@@ -70,7 +70,7 @@ And save the downloaded file
 
 </center>
 
-- In order to make use of [Self-Service Actions using GitHub Workflow](../../../../self-service-actions/github-workflow/github-workflow.md), please contact us at support@getport.io.
+- In order to make use of [Self-Service Actions using GitHub Workflow](/self-service-actions/github-workflow/github-workflow.md), please contact us at [support.port.io](http://support.port.io/).
 
 :::
 
diff --git a/archive/self-service-actions/self-service-actions.md b/archive/self-service-actions/self-service-actions.md
@@ -22,5 +22,5 @@ Port enables developer Self-Service in 2 distinct ways:
 The power of Port's self-service actions is enabled by using one of the following: [Webhooks](./webhook/webhook.md), [Kafka topics](./kafka/kafka.md) and [GitHub Workflow](./github-workflow/github-workflow.md). Go to each self-service action type's respective page to learn more and see practical examples.
 
 :::note
-In order to make use of Port's Kafka topics for Self-Service Actions, please contact us at support@getport.io
+In order to make use of Port's Kafka topics for Self-Service Actions, please contact us at [support.port.io](http://support.port.io/)
 :::
diff --git a/contributor-license-agreement.txt b/contributor-license-agreement.txt
@@ -3,7 +3,7 @@ Port Documentation Contributor License Agreement
 Thank you for your interest in the Port product documentation (the "Documentation").
 To clarify the intellectual property license granted to users of the Documentation from any person or entity, GtPort.io Ltd. (the "Company") must have on file a signed Contributor License Agreement ("CLA") from each Contributor, indicating agreement with the license terms below. 
 
-This agreement is for your protection as a Contributor as well as the protection of the Company and its users. It does not change your rights to use your own Contributions for any other purpose. Please complete and sign this Agreement, and then email a signed copy to support@getport.io only (do not copy any other persons or lists). Read this document carefully before signing and keep a copy for your records. 
+This agreement is for your protection as a Contributor as well as the protection of the Company and its users. It does not change your rights to use your own Contributions for any other purpose. Please complete and sign this Agreement, and then email a signed copy to support@port.io only (do not copy any other persons or lists). Read this document carefully before signing and keep a copy for your records. 
 
 Full name: _____________________________________________________ 
 
diff --git a/docs/actions-and-automations/setup-backend/gitlab-pipeline/self-hosted.md b/docs/actions-and-automations/setup-backend/gitlab-pipeline/self-hosted.md
@@ -22,7 +22,7 @@ This page will introduce the agent and guide you through the installation and co
 
 ## Prerequisites
 
-- Connection credentials to Kafka are required. To obtain them, contact us using chat/Slack/mail to [support@getport.io](mailto:support@getport.io).
+- Connection credentials to Kafka are required. To obtain them, contact us using chat/Slack/support site at [support.port.io](http://support.port.io/).
 - [Helm](https://helm.sh) must be installed in order to install the relevant chart.
 - In order to trigger a GitLab Pipeline, you need to have a [GitLab trigger token](https://docs.gitlab.com/ee/ci/triggers/).
 
diff --git a/docs/actions-and-automations/setup-backend/webhook/circle-ci/circle-ci.md b/docs/actions-and-automations/setup-backend/webhook/circle-ci/circle-ci.md
@@ -16,7 +16,7 @@ You can implement this action in two ways:
 - A Circle CI [personal API token](https://app.circleci.com/settings/user/tokens).
 - If you choose to implement using the Execution Agent, you will need to:
   - Install [Helm](https://helm.sh) on your infrastructure
-  - Contact Port [support](mailto:support@getport.io) to set up a Kafka topic for your organization.
+  - Contact Port [support](http://support.port.io/) to set up a Kafka topic for your organization.
 
 ## Set up data model
 
diff --git a/docs/actions-and-automations/setup-backend/webhook/kafka/examples/__changelog-basic-change-listener-using-aws-lambda.md b/docs/actions-and-automations/setup-backend/webhook/kafka/examples/__changelog-basic-change-listener-using-aws-lambda.md
@@ -9,7 +9,7 @@ In this guide, we will show how to deploy a new `AWS Lambda function`, that will
 ## Prerequisites
 
 :::note
-To follow this example, please contact us using chat/Slack/mail to [support@getport.io](mailto:support@getport.io) to receive a dedicated Kafka topic.
+To follow this example, please contact us using chat/Slack/support site at [support.port.io](http://support.port.io/) to receive a dedicated Kafka topic.
 :::
 
 - AWS CLI installed and configured to your desired AWS account;
diff --git a/docs/actions-and-automations/setup-backend/webhook/port-execution-agent/port-execution-agent.md b/docs/actions-and-automations/setup-backend/webhook/port-execution-agent/port-execution-agent.md
@@ -13,7 +13,7 @@ Our Port agent is open source - see it [**here**](https://github.com/port-labs/p
 :::
 
 :::note Request Kafka Topic
-To use the execution agent, please contact us using chat/Slack/mail to [support@getport.io](mailto:support@getport.io) to receive a dedicated Kafka topic.
+To use the execution agent, please contact us using chat/Slack/support site at [support.port.io](http://support.port.io/) to receive a dedicated Kafka topic.
 :::
 
 The data flow when using the Port execution agent is as follows:
diff --git a/docs/actions-and-automations/setup-backend/webhook/terraform-cloud/terraform-cloud.md b/docs/actions-and-automations/setup-backend/webhook/terraform-cloud/terraform-cloud.md
@@ -21,7 +21,7 @@ You can implement this action in two ways:
 
 - If you choose to implement using the Execution Agent, you will need to:
   - Install [Helm](https://helm.sh) on your infrastructure
-  - Contact Port [support](mailto:support@getport.io) to set up a Kafka topic for your organization.
+  - Contact Port [support](http://support.port.io/) to set up a Kafka topic for your organization.
 
 ## Set up data model
 
diff --git a/docs/api-reference/pages.mdx b/docs/api-reference/pages.mdx
@@ -19,5 +19,5 @@ The Pages API is currently in beta, in its current form it lacks certain validat
 
 If you choose to use the Pages API please understand this risk.
 
-In case you use the Pages API and encounter issues, please reach out to `support@getport.io` for assistance.
+In case you use the Pages API and encounter issues, please reach out at [support.port.io](http://support.port.io/) for assistance.
 :::
diff --git a/docs/api-reference/security.mdx b/docs/api-reference/security.mdx
@@ -51,7 +51,7 @@ In step 5 of the guide, you are required to provide the **Service name**, which
 
 **Note:** In case your AWS resources are in a different region than the ones Port's PrivateLinks are hosted at, refer to step 6 of the guide to setup a cross region connection.
 
-After following the guide, please contact Port's support team using chat/Slack/mail to [support@getport.io](mailto:support@getport.io) and we will finalize the setup.
+After following the guide, please contact Port's support team using chat/Slack/mail to [support.port.io](http://support.port.io/) and we will finalize the setup.
 
 ## IP address restriction (beta)
 
@@ -73,7 +73,7 @@ Both when using Port's UI and when making an API request from an IP address whic
 
 :::info providing the IP restriction list
 
-Managing a customer's IP restriction list is performed by Port's staff, to specify your IP restriction list contact us using chat/Slack/mail to [support@getport.io](mailto:support@getport.io).
+Managing a customer's IP restriction list is performed by Port's staff, to specify your IP restriction list contact us using chat/Slack/mail to [support.port.io](http://support.port.io/).
 
 :::
 
diff --git a/docs/build-your-software-catalog/custom-integration/S3-integrations.md b/docs/build-your-software-catalog/custom-integration/S3-integrations.md
@@ -241,4 +241,4 @@ If any entities were created but failed to ingest, you will see an indicative er
 
 <h3>Data is not propagating from S3 to Port</h3>
 If you're sure the Airbyte integration is working properly, there are no records in the Audit Log, and the "Load latest event" button does not produce an event in the corresponding box, there might be an issue with the pipeline set up by Port.  
-In this case, contact us using chat/Slack/mail to [support@getport.io](mailto:support@getport.io) and our support team will assist in diagnosing and solving the issue.
+In this case, contact us using chat/Slack/support site to [support.port.io](http://support.port.io/) and our support team will assist in diagnosing and solving the issue.
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/apm-alerting/dynatrace/dynatrace.md b/docs/build-your-software-catalog/sync-data-to-catalog/apm-alerting/dynatrace/dynatrace.md
@@ -1632,7 +1632,7 @@ Here is an example of the payload structure from Dynatrace:
       },
       {
         "integrationType": "EMAIL",
-        "email": "support@getport.io"
+        "email": "support@port.io"
       },
       {
         "integrationType": "SLACK",
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/git/github/self-hosted-installation.md b/docs/build-your-software-catalog/sync-data-to-catalog/git/github/self-hosted-installation.md
@@ -77,7 +77,7 @@ You will need your Port `ORG_ID`, `CLIENT_ID` and `CLIENT_SECRET`.
 
 :::
 
-In order to make use of [Self-Service Actions using GitHub Workflow](../../../../actions-and-automations/setup-backend/github-workflow/github-workflow.md), please contact us at support@getport.io.
+In order to make use of [Self-Service Actions using GitHub Workflow](../../../../actions-and-automations/setup-backend/github-workflow/github-workflow.md), please contact us at [support.port.io](http://support.port.io/).
 
 ## Docker
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/incident-management/pagerduty/pagerduty.md b/docs/build-your-software-catalog/sync-data-to-catalog/incident-management/pagerduty/pagerduty.md
@@ -1368,7 +1368,7 @@ For relevant guides and examples, see the [guides section](https://docs.port.io/
 
 ## Support
 
-For any questions or issues, contact us at [support@getport.io](mailto:support@getport.io) or via our [Community Slack channel](https://port.io/community).
+For any questions or issues, contact us at [support.port.io](http://support.port.io/) or via our [Community Slack channel](https://port.io/community).
 
 ## Alternative installation via webhook
 While the Ocean integration described above is the recommended installation method, you may prefer to use a webhook to ingest data from PagerDuty. If so, use the following instructions:
diff --git a/docs/guides/all/execution-basic-runner-using-aws-lambda.md b/docs/guides/all/execution-basic-runner-using-aws-lambda.md
@@ -13,7 +13,7 @@ In this guide, you will deploy a new `AWS Lambda function` that will subscribe t
 ## Prerequisites
 
 :::note
-To follow this example, please contact us using chat/Slack/mail to [support@getport.io](mailto:support@getport.io) to receive a dedicated Kafka topic.
+To follow this example, please contact us using chat/Slack/support site to [support.port.io](http://support.port.io/) to receive a dedicated Kafka topic.
 :::
 
 - AWS CLI installed and configured to your desired AWS account;
diff --git a/docs/guides/all/ingest-hibob-data-via-airbyte-s3-and-webhook.md b/docs/guides/all/ingest-hibob-data-via-airbyte-s3-and-webhook.md
@@ -22,7 +22,7 @@ This guide will demonstrate how to ingest HiBob data into Port using [Airbyte](h
 
 - Ensure you have a Port account and have completed the [onboarding process](https://docs.port.io/quickstart).
 
-- This feature is part of Port's limited-access offering. To obtain the required S3 bucket, please contact our team directly via chat, [Slack](https://www.getport.io/community), or [e-mail](mailto:support@getport.io), and we will create and manage the bucket on your behalf.
+- This feature is part of Port's limited-access offering. To obtain the required S3 bucket, please contact our team directly via chat, [Slack](https://www.getport.io/community), or the[support site](http://support.port.io/), and we will create and manage the bucket on your behalf.
 
 - Access to an available Airbyte app (can be cloud or self-hosted) - for reference, follow the [quick start guide](https://docs.airbyte.com/using-airbyte/getting-started/oss-quickstart).
 
diff --git a/docs/guides/all/ingest-okta-data-via-airbyte-s3-and-webhook.md b/docs/guides/all/ingest-okta-data-via-airbyte-s3-and-webhook.md
@@ -22,7 +22,7 @@ This guide will demonstrate how to ingest Okta data into Port using [Airbyte](ht
 
 - Ensure you have a Port account and have completed the [onboarding process](https://docs.port.io/quickstart).
 
-- This feature is part of Port's limited-access offering. To obtain the required S3 bucket, please contact our team directly via chat, [Slack](https://www.getport.io/community), or [e-mail](mailto:support@getport.io), and we will create and manage the bucket on your behalf.
+- This feature is part of Port's limited-access offering. To obtain the required S3 bucket, please contact our team directly via chat, [Slack](https://www.getport.io/community), or the[support site](http://support.port.io/), and we will create and manage the bucket on your behalf.
 
 - Access to an available Airbyte app (can be cloud or self-hosted) - for reference, follow the [quick start guide](https://docs.airbyte.com/using-airbyte/getting-started/oss-quickstart).
 
diff --git a/docs/guides/all/ingest-slack-data-via-airbyte-s3-and-webhook.md b/docs/guides/all/ingest-slack-data-via-airbyte-s3-and-webhook.md
@@ -21,7 +21,7 @@ This guide will demonstrate how to ingest Slack channels and channel membership
 
 - Ensure you have a Port account and have completed the [onboarding process](https://docs.port.io/quickstart).
 
-- This feature is part of Port's limited-access offering. To obtain the required S3 bucket, please contact our team directly via chat, [Slack](https://www.getport.io/community), or [e-mail](mailto:support@getport.io), and we will create and manage the bucket on your behalf.
+- This feature is part of Port's limited-access offering. To obtain the required S3 bucket, please contact our team directly via chat, [Slack](https://www.getport.io/community), or the [support site](http://support.port.io/), and we will create and manage the bucket on your behalf.
 
 - Access to an available Airbyte app (can be cloud or self-hosted) - for reference, follow the [quick start guide](https://docs.airbyte.com/using-airbyte/getting-started/oss-quickstart).
 
diff --git a/docs/guides/all/ingest-slack-data-via-fivetran-s3-and-webhook.md b/docs/guides/all/ingest-slack-data-via-fivetran-s3-and-webhook.md
@@ -20,7 +20,7 @@ This guide will demonstrate how to ingest Slack channels and channel membership
 
 - Ensure you have a Port account and have completed the [onboarding process](https://docs.port.io/quickstart).
 
-- This feature is part of Port's limited-access offering. To obtain the required S3 bucket, please contact our team directly via chat, [Slack](https://www.getport.io/community), or [e-mail](mailto:support@getport.io), and we will create and manage the bucket on your behalf.
+- This feature is part of Port's limited-access offering. To obtain the required S3 bucket, please contact our team directly via chat, [Slack](https://www.getport.io/community), or the [support site](http://support.port.io/), and we will create and manage the bucket on your behalf.
 
 :::tip Important
 
diff --git a/docs/sso-rbac/sso-providers/oidc/azure-ad.md b/docs/sso-rbac/sso-providers/oidc/azure-ad.md
@@ -89,7 +89,7 @@ To complete the process you will need to contact us to receive the information y
 
    <SSOEndpoints/>
 
-   We will provide your `{CONNECTION_NAME}` (Contact us using chat/Slack/mail to [support@getport.io](mailto:support@getport.io)).
+   We will provide your `{CONNECTION_NAME}` (Contact us using chat/Slack/mail to [support.port.io](http://support.port.io/)).
 
    2.2 **Publisher domain**: Select the domain matching your user emails (for example `getport.io`).
 
diff --git a/docs/sso-rbac/sso-providers/oidc/oidc.md b/docs/sso-rbac/sso-providers/oidc/oidc.md
@@ -17,7 +17,7 @@ In order to integrate Port with an OIDC SSO application, you will need to do the
    - Login URI: 
      <SSOEndpoints/>
      :::note
-     We will provide your `{CONNECTION_NAME}` (Contact us using chat/Slack/mail to [support@getport.io](mailto:support@getport.io)).
+     We will provide your `{CONNECTION_NAME}` (Contact us using chat/Slack/mail to [support.port.io](http://support.port.io/)).
      :::
 3. Expose the application to your organization by either granting access to everyone or restricting it to specific roles.
 4. Share information about your SSO application:
diff --git a/docs/sso-rbac/sso-providers/oidc/okta.md b/docs/sso-rbac/sso-providers/oidc/okta.md
@@ -72,7 +72,7 @@ Get your `Okta Domain` by clicking on your user mail at the top-right corner of
 
 Under `General` tab:
 
-1. Copy the `Client ID` and send it to Port along with the `Okta Domain` from the previous step (using chat/Slack/mail to [support@getport.io](mailto:support@getport.io)).
+1. Copy the `Client ID` and send it to Port along with the `Okta Domain` from the previous step (using chat/Slack/mail to [support.port.io](http://support.port.io/)).
 
    ![Okta app settings](/img/sso/okta/OktaAppSettingsPage.png)
 
@@ -93,7 +93,7 @@ Under `General` tab:
    <SSOEndpoints/>
 
    :::note
-   We will provide your `{CONNECTION_NAME}` (Contact us using chat/Slack/mail to [support@getport.io](mailto:support@getport.io)).
+   We will provide your `{CONNECTION_NAME}` (Contact us using chat/Slack/mail to [support.port.io](http://support.port.io/)).
    :::
 
    ![Okta app settings login flow](/img/sso/okta/OktaAppLoginflowSettings.png)
diff --git a/docs/sso-rbac/sso-providers/oidc/onelogin.md b/docs/sso-rbac/sso-providers/oidc/onelogin.md
@@ -60,7 +60,7 @@ In the Port app, go to the `Configuration` menu and follow these steps:
 <SSOEndpoints/>
 
 :::note
-We will provide your `{CONNECTION_NAME}` (Contact us using chat/Slack/mail to [support@getport.io](mailto:support@getport.io)).
+We will provide your `{CONNECTION_NAME}` (Contact us using chat/Slack/mail to [support.port.io](http://support.port.io/)).
 :::
 
 2. Under `Redirect URI's` set: `https://auth.getport.io/login/callback`.
diff --git a/docs/sso-rbac/sso-providers/saml/google-workspace.md b/docs/sso-rbac/sso-providers/saml/google-workspace.md
@@ -99,7 +99,7 @@ Press `Continue`.
 - `Entity ID` - `urn:auth0:port-prod:{CONNECTION_NAME}`
 
 :::note
-We will provide your `{CONNECTION_NAME}` (Contact us using chat/Slack/mail to [support@getport.io](mailto:support@getport.io)).
+We will provide your `{CONNECTION_NAME}` (Contact us using chat/Slack/mail to [support.port.io](http://support.port.io/)).
 :::
 
 Press `Continue`
diff --git a/docs/sso-rbac/sso-providers/saml/jumpcloud.md b/docs/sso-rbac/sso-providers/saml/jumpcloud.md
@@ -58,7 +58,7 @@ Click `activate`.
    2. Copy the `IDP URL` from the SSO tab
       ![Jumpcloud IDP URL](/img/sso/jumpcloud/JumpcloudIDPUrl.png)
 
-6. Via chat/Slack/mail to [support@getport.io](mailto:support@getport.io), provide Port with the downloaded `certificate.pem` file, and the copied `IDP URL`.
+6. Via chat/Slack/mail to [support.port.io](http://support.port.io/), provide Port with the downloaded `certificate.pem` file, and the copied `IDP URL`.
 
 :::note
 After providing the `certificate.pem` file and the the `IDP URL` to Port, you will be provided with you with your `{CONNECTION_NAME}`. Replace the following occurrences with the provided value.
diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
@@ -106,7 +106,7 @@ After the `error_description`, you can see `User%20is%20not%20assigned%20to%20th
 <summary><b>Answer (click to expand)</b></summary>
 
 When using the free tier, Port allows you to be connected to a single organization. If your colleague is in another organization, you will not be able to invite him/her.  
-Reach out to us using chat/Slack/mail to [support@getport.io](mailto:support@getport.io), and we will help you resolve the issue.
+Reach out to us using chat/Slack/support site at [support.port.io](http://support.port.io/), and we will help you resolve the issue.
 
 </details>
 
@@ -126,7 +126,7 @@ If you are facing issues after installing an Ocean integration, follow these ste
 3. In your [builder](https://app.getport.io/settings/data-model) page, make sure that the new `blueprints` were created with the correct properties/relations.
 4. If you tried to install a `self-hosted` integration, check the integration's documentation to ensure you included the necessary parameters.
 
-If you are still facing issues, reach out to us using chat/Slack/mail to [support@getport.io](mailto:support@getport.io), and we will help you resolve the issue.
+If you are still facing issues, reach out to us using chat/Slack/mail to [support.port.io](http://support.port.io/), and we will help you resolve the issue.
 
 </details>
 
