> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/integrations/saas-applications/figma.md).
# Figma
### About Figma
Figma is a collaborative design platform used across product, design, and engineering teams. Connecting Figma to Harmony gives IT teams visibility into who is using Figma, what seat type they hold, and how frequently they sign in — enabling license optimization and access governance.
{% hint style="info" %}
This integration requires **Figma Enterprise plan**. It is read-only — Harmony pulls data from Figma but does not modify your Figma organization.
{% endhint %}
### What the Figma integration enables
| Capability | Description |
| -------------------- | ----------------------------------------------------------------------- |
| Sign-In Activity | Track user login trends to identify active vs. inactive accounts |
| User Inventory | Surface all Figma users with their seat types (Full, Dev, Collab, View) |
| License Optimization | Identify underutilized seats and right-size your Figma subscription |
### Prerequisites
* **Figma Enterprise plan** (required for both Activity Logs and SCIM APIs)
* **Organization Admin** role in Figma
* **Harmony Account**: Active Harmony workspace
### Connect Figma to Harmony
#### Step 1: Create a Plan Access Token
A Plan Access Token provides API access scoped to your organization without being tied to an individual user account.
1. Go to [figma.com/developers/tokens](https://www.figma.com/developers/tokens)
2. Click **Generate REST API token**
3. Enter a name (e.g. `Harmony Integration`) and description
4. Set expiration (up to 365 days)
5. On the **Choose scopes** page, select `org:activity_log_read`
6. On the **Choose resources** page, select **All resources**
7. Click **Create** and copy the token immediately — it won't be shown again
For full details, see [Figma's Plan Access Token documentation](https://developers.figma.com/docs/rest-api/plan-access-tokens/).
{% hint style="warning" %}
Creating a Plan Access Token requires multi-factor authentication. Unless your organization uses SSO, the admin must set up Figma 2FA first.
{% endhint %}
#### Step 2: Generate a SCIM API Token (Optional)
The SCIM token enables user inventory with seat type information. If you skip this step, Harmony will still track sign-in activity but won't have a complete user list with seat assignments.
1. Go to **Admin Settings** > **Login and Provisioning** > **SCIM Provisioning**
2. Click **Generate Token**
3. Copy the token immediately — it won't be shown again
4. Note the **Tenant ID** from **Admin Settings** > **Login and Provisioning** > **SAML SSO** (a numeric string like `964615200748176016`)
#### Step 3: Navigate to Integrations
1. Log in to your Harmony dashboard
2. Go to **Settings** > **Integrations**
3. Find **Figma** under **SaaS Applications** and click **Connect**
#### Step 4: Enter Credentials
1. Enter your **Plan Access Token** (from Step 1)
2. Optionally enter your **SCIM API Token** (from Step 2)
3. Optionally enter your **SCIM Tenant ID** (from Step 2)
4. Click **Connect**
### What Harmony Syncs
**From Figma Activity Logs:**
* Sign-in events (user email, timestamp, IP address)
* Login frequency and trends per user
**From Figma SCIM (if configured):**
* Users (name, email, active status)
* Seat type per user (Full Design, Dev Mode, Collaborator, Viewer)
* Job title and department (if provisioned via IdP)
### Use Cases
License Reclamation
Identify users with paid Figma seats (Full or Dev) who haven't signed in recently. Downgrade them to Viewer seats to reduce costs.
Seat Type Audit
Compare actual Figma usage patterns against assigned seat types. Users with Full Design seats who only view files may be better served by a Viewer or Collaborator seat.
Offboarding Verification
Confirm deactivated employees no longer hold active Figma seats as part of offboarding workflows.
---
# 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://docs.harmony.io/integrations/saas-applications/figma.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.