> 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-cloud-posture-management/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/figma.md).

# Figma

Use Figma data with Cortex Cloud.

The capabilities and sub-capabilities listed for this connector are available with any active Cortex XSIAM or Cortex Cloud Posture Security license.

This connector includes the following capabilities and sub-capabilities (if applicable):

* **SaaS Posture Configuration Monitoring:** Detect, monitor and alert on settings of your SaaS application.
  * **saas-posture-config-remediation:** Help remediate the misconfigured security settings of your SaaS application.

### How to configure the Figma connector

To access Figma, Cortex Cloud requires the following information, which you will specify during the connection process.

* **Organization ID:** A unique identifier for your Figma organization, visible in the URL of your Figma homepage.
* **Access Token:** A personal REST API token generated from the Figma developer console. Cortex Cloud uses this token to authenticate to the Figma API.

> **Note:** To generate an Access Token, your Figma account must have Multi-Factor Authentication (MFA) configured. If you see a two-factor authentication warning during token creation, enable MFA on your account before proceeding.

Perform the following procedures in the order that they appear below.

#### Task 1: Identify Your Organization ID

1. Log in to your Figma account at <https://www.figma.com>.
2. On the homepage, locate your Organization ID in the URL. The ID is the number that appears after `/files/`.

   For example, in the URL `https://www.figma.com/files/123/recents-and-sharing?fuid=456`, the Organization ID is `123`.
3. Copy the Organization ID and store it in a text file.

   > Do not continue to the next step unless you have copied the Organization ID. You must provide this value to Cortex Cloud during the onboarding process.

#### Task 2: Generate an Access Token

1. Navigate to the Figma developer console at <https://www.figma.com/developers/tokens> and log in.
2. Click **Generate REST API Token**.
3. In the dialog, enter a **Name** and **Description** for the token, set **Expiration** to **365 days**, and click **Next**.
4. In the **Choose Scopes** section, under **Organizations**, select the `org:activity_log_read` scope. Click **Next**.
5. In the **Choose Resources** section, keep **All Resources** selected and click **Create**.
6. Copy the generated access token and store it securely.

   > Do not continue to the next step unless you have copied the access token. This value is shown only once and cannot be retrieved after you close the dialog. You must provide it to Cortex Cloud during the onboarding process.

#### Task 3: Connect Figma to Cortex Cloud

1. In Cortex Cloud, navigate to **Settings** → **Data Sources & Integrations**.
2. Click **+ Add new**.
3. In the **Add Data Source** page, search for Figma.
4. Under **Recommended**, hover over the new Figma integration and click **Add Instance** to launch the configuration wizard.
5. Under the **Capabilities** tab, enter a name for your application.
6. Select **Security Posture** under **Default Capabilities**. Click **Next**.
7. Under the **Connection** tab, enter the **Organization ID** and **Access Token** details.
8. Under the **Configuration** tab, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments.
9. A confirmation message shows that Figma is successfully connected. Confirm the **Summary** details and click **Save instance**.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/figma.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
