> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/cloud-security/cortex-cloud-saas-security/onboard-a-supported-saas-application/onboard-monday.com.md). # Onboard Monday.com For SaaS Security to detect posture risks in your monday.com instance, you must onboard your monday.com instance to SaaS Security. Through the onboarding process, SaaS Security logs in to monday.com using administrator account credentials. SaaS Security uses this account to scan your monday.com instance for misconfigured settings. If there are misconfigured settings, SaaS Security suggests a remediation action based on best practices. To onboard your monday.com instance, complete the following actions: * Collect information for connecting to your monday.com instance * Connect SaaS Security to your monday.com instance *** ### Step 1: Collect Information for Connecting to Your monday.com Instance To access your monday.com instance, SaaS Security requires connection information. During the onboarding process, you specify the following required and optional information. | Item | Description | | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Email | The login email address of a monday.com administrator. Required Permissions: You must supply SaaS Security with Admin credentials to your monday.com account. | | Password | The password of the monday.com administrator. | | Account Domain | The custom domain for your monday.com account. After you log in to monday.com, this domain is part of your monday.com URL in the format \.monday.com. | | MFA Secret Key | (Optional) A key that is used to generate one-time passcodes for multi-factor authentication. | As you complete the following steps, make note of the values of the items described in the preceding table. You will need to enter these values during onboarding to access your monday.com instance from SaaS Security. 1. Identify the monday.com administrator whose credentials you will supply to SaaS Security. Required Permissions: You must supply SaaS Security with Admin credentials to your monday.com account. 2. Identify your monday.com account domain. After you log in to monday.com, the account domain is a unique subdomain included in the monday.com URL in the format \.monday.com. You can also identify your account domain from your profile: 1. Open a web browser and go to the monday.com login page at [auth.monday.com/auth/login\_monday](https://auth.monday.com/auth/login_monday). 2. Log in to the administrator account that you identified. 3. Navigate to the Administration page. Locate your account avatar and select \ > Administration. 4. On the Administration page, select General > Profile. The Account URL (Web Address) field shows your account domain. 5. (Optional) Generate and copy an MFA secret key. MFA provides an extra layer of security when accessing the monday.com administrator account. To enable this extra layer of security, you must configure the administrator account for MFA that uses time-based one-time passcodes. Like an authenticator app, SaaS Security uses the MFA secret key for passcode generation. 1. Decide which authenticator app you will use and download it to your cellphone. You can use any authenticator app that generates time-based one-time passcodes (TOTP), such as Microsoft Authenticator or Google Authenticator. 2. Open a web browser and go to [auth.monday.com/auth/login\_monday](https://auth.monday.com/auth/login_monday) and log in to the administrator account. 3. Navigate to the Administration page. Locate your account avatar and select \ > Administration. 4. On the Administration page, select Security > Login. 5. Locate the Two-Factor Authentication section and click Enable Two-Factor Authentication. 6. When monday.com prompts you to choose your authentication method, select Authentication App and click Continue. 7. A pop-up window displays your MFA secret key as a QR code. Do not scan the QR code. Click Copy code instead to display a text version of the MFA secret key. 8. Copy and paste the text version of the MFA secret key into a text file. **Note**: Do not continue to the next step unless you have copied the MFA secret key. You will provide this key to SaaS Security during the onboarding process. 9. Continue configuring your authentication app by scanning the QR code or by manually entering the MFA secret key. *** ### Step 2: Connect SaaS Security to Your monday.com Instance By adding a monday.com app in Cortex, you enable SaaS Security to connect to your monday.com instance. 1. Log in to Cortex. 2. Select **Settings > Data Sources and Integrations > Add New**. You can use the Search bar to find the app you want to connect to. 3. Click the monday.com tile. 4. Under **Capabilities**, enter a name for your application. 5. Select Security Posture under Default Capabilities and click Next. 6. Under **Connections**, enter the administrator login credentials, your account domain, and, optionally, the MFA secret key. 7. Under **Configurations**, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments. 8. Click **Next** to complete the onboarding validation process. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/cloud-security/cortex-cloud-saas-security/onboard-a-supported-saas-application/onboard-monday.com.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.