# SMAX---Enable-Pendo-for-SMAX-tenant_688982184 ## Introduction Integrate the SaaS instance of Pendo into SMAX. The integration is configured to be released only for SMAX SaaS trial tenants and non-FedRAMP environments. The **Pendo API key** needs to be configured for SMAX SaaS farms that require the integration to be enabled. ## Steps to configure the Pendo API key Get the values.yaml file for Helm by running the command below: ``` helm get values -n > my-values.yaml ``` Open the *my-values.yaml* file and copy the snippet below into it with the correct indentation (by default 2 spaces per indentation level) and format style. ``` xruntime: xruntime-gateway: PENDO_API_KEY: "" ``` *Set PENDO\_API\_KEY to “94956982-4d2a-4052-7cf5-113fdbb85ba6” and save the change.* **Note:** The Pendo API key typically won't change, but if it does, contact PM Dean (dclayton2@opentext.com) for the new key. ![](attachments/688982184/688982167.png) Run the command below to apply the change: ``` helm upgrade -n -f my-values.yaml ``` ## Confirm that the current farm is SaaS and non-FedRAMP Check the ESM *itsma-common-configmap* by running the command below: ``` kubectl edit configmap itsma-common-configmap -n ``` Make sure ***is\_fedramp*** is *false* and ***is\_saas*** is *true*: ![](attachments/688982184/688982176.png) If they are not, correct their values and restart the *itom-xruntime-gateway* pod by running the command below: ``` kubectl rollout restart deployment itom-xruntime-gateway -n ``` ## Check if Pendo-SMAX integration works well Log in to the trial tenant as an admin. If this is your first login, you will see the following screen. ![](attachments/688982184/688982181.png) Regardless of whether you click 'Deploy sample data' or 'No, thanks,' a Pendo consent dialog will pop up. ## Attachments: [image-2025-2-5\_9-53-37.png](attachments/688982184/688982167.png) (image/png) [image-2025-2-5\_9-57-22.png](attachments/688982184/688982176.png) (image/png) [image-2025-2-5\_9-57-50.png](attachments/688982184/688982181.png) (image/png)