Figma

Overview
How to connect
Automated checks
Useful links

DSALTA connects to Figma using read-only API access to collect compliance evidence automatically. Data feeds into your Data Library modules.

Read-only access. DSALTA never modifies, creates, or deletes resources in your Figma environment.

DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

What DSALTA reads

DSALTA reads the Figma account that authorized the connection — a single row on your Access page. Figma’s API does not expose a team member list to this integration, so the page shows the connected account rather than your whole team.It calls these Figma endpoints:

/v1/me

Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Figma environment.

Troubleshooting

Integration shows Disconnected

There is no Reconnect button. Open Integrations → Connected, click Manage on the Figma card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from Figma. This usually happens when API tokens expire.

Data is not syncing

Verify the connected account still holds the permissions this integration requires. Then open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Sync from integrations at the top right. That button refreshes every connected integration at once — there is no per-integration sync control.

DSALTA requests these scopes: current_user:read.

Open the integration

In the DSALTA sidebar, go to Integrations, find Figma, and click Connect.

Authorize access

A secure Figma window opens. Sign in if prompted and approve the request. DSALTA does not ask you to choose which resources to monitor — the connection covers everything the credential you authorize can read.Sign in as the Figma account you want reviewed. That account becomes the only row on your Access page — DSALTA reads GET /v1/me and records its handle, email and Figma user id, with the role shown as “Member”. Use an account whose email exists on your People page, or both checks will flag it.current_user:read is the only scope DSALTA requests. It returns the signed-in user’s id, email, handle and avatar URL — no files, projects, comments, or team content. Nothing you have in Figma is readable through this connection.

There is no way to get your whole Figma team onto the Access page through this integration. A full member roster requires Figma Enterprise’s org admin endpoint (/v1/orgs/{org_id}/members), which needs an org id and an Enterprise plan and is not part of this connection. If you need org-wide Figma access review, drive it from your IdP integration instead.

DSALTA's Link Figma Account panel warning that a pop-up will open, with a Connect button

Once connected, Figma appears on the Connected tab and the checks below begin reporting after the first sync.

Each check below re-runs once a day, at 02:00 America/New_York, while this integration is connected. Click any check for step-by-step remediation guidance.

Check	Severity	What it verifies
User access to Critical System should be valid	Info	Checks that everyone with Figma access is an active employee on the People page.
Offboarded users should not have active access	High	Checks that offboarded employees no longer have active Figma access.

Topic	Link
Setup	Figma REST API and OAuth scopes
General	Figma website
DSALTA	Connection error messages

Getting Connected

Identity Providers

Cloud Infrastructure

Code Repositories

Security & Monitoring

Databases

SaaS & Productivity

What DSALTA reads

Troubleshooting

​What DSALTA reads

​Troubleshooting

What DSALTA reads

Troubleshooting