https://api.figma.com), using a plan access token that an organization admin creates in Figma. Configview sends only GET requests, plus one read-only query to the developer log. It never creates, changes or deletes anything in Figma.
You will end up with 1 required secret (FIGMA_ACCESS_TOKEN) and 2 optional secrets (FIGMA_TEAM_IDS, FIGMA_PLAN_ID) in Configview when setup is complete.
Scope of this integration today. Configview reads which folders are open to the whole plan, which files can be opened by anyone with the link, your webhooks (which host they send to, never the passcode), the organization activity log (sharing, permission, seat, guest, token, plugin and security-setting changes), which API and MCP tokens are in use, and AI credit use per person. It does not read file content, layers, comments, thumbnails, variables or dev resources, and it does not read file names except for files that are shared by public link.
What you need
- A Figma Organization or Enterprise plan. Plan access tokens exist only on those plans.
- An organization admin to create the token (Figma asks them for 2FA or SSO).
- For the activity log, AI usage and developer log you need the Enterprise plan (the developer log needs the Governance tier). On other plans those collectors skip themselves and their tables stay empty. That does not count as a failure.
- The numbers of the teams you want inventoried (step 3). Figma has no API that lists teams.
Step 1: Open the Figma page in Configview
Open Configview in a second browser tab and leave it open:https://{companyname}.configview.com/admin/integrations/figma
Step 2: Create the plan access token
- As an organization admin open
https://www.figma.com/developers/tokens - Choose Plan access tokens and Generate new token
- Name it
Configview, then choose an expiration. Figma allows at most 365 days. - Tick only these read scopes and nothing else:
file_metadata:readfolders:readteams:readwebhooks:read- Enterprise only:
org:activity_log_read,org:ai_metering_usage_read,org:developer_log_read
- Under resources choose All resources, or Only selected resources and list your teams. A token limited to some teams only sees those teams.
- Click Create and copy the token. Figma shows it once.
- In the Configview tab paste it into
FIGMA_ACCESS_TOKENunder Credentials and click the save icon
FIGMA_ACCESS_TOKEN.
Do not tick any write scope, files:read or org:discovery_read: Configview does not need them and they reach file content.
Step 3: Add the team IDs (optional but recommended)
Without team IDs the folder, file and file-sharing collectors are skipped.- In Figma open a team page in the file browser
- Copy the number after
/team/in the address bar. Forhttps://www.figma.com/files/181033233908053158/team/1535685101263221741/Designthe team ID is1535685101263221741. - Paste one or more IDs, separated by commas, into
FIGMA_TEAM_IDSin Configview (pasting the team page addresses also works) and click the save icon
Step 4: Add the plan ID (optional)
FIGMA_PLAN_ID lets Configview list every webhook in the plan in one request. The plan API ID appears as plan_api_id on any webhook Figma returns. If you leave it empty, webhooks are listed per team from FIGMA_TEAM_IDS instead.
Step 5: Connect and verify
- Click Connect. Configview creates its tables and schedules every collector at your default run time. Stop any you don’t want under Collectors:
- Click Verify now. The health check reads the token, then tries one small request for each area you configured.
- 401. The token is wrong, expired or was revoked. Create a new one.
- 403 on the team. The token does not have
folders:read, or its resource list does not include that team. - 404 on the team. The team ID is wrong. Copy it again from the team page address.
- Activity log or AI usage shows as skipped. Your plan is not Enterprise, or the token lacks that scope. Nothing to fix unless you want that area.
Data Tables
Each table has arun_at column. Every table keeps only the newest run.
Things worth knowing
Link access.link_access is view or edit when anyone with the link can open or edit the file (public), org_view or org_edit when only people in your organization can, and inherit when the folder decides. figma_folders.sharing_audience is plan_view, plan_edit, workspace_view, workspace_edit or invite_only.
File names are private. A file name is free text written by a person. Configview stores it only for files that are public by link, so a risky file can be found. Everywhere else it keeps the file key.
No member list. Figma has no REST endpoint that lists the people in an organization. The roster in figma_seen_users is built from the people who appear as the actor in the activity log in the last 90 days, so someone who has not acted for 90 days is not in it. Figma’s SCIM API can list users, but its documentation says reading GET /Users “will bind the user accounts to the SCIM table”, a change to your organization, so Configview does not call it.
The activity log. Configview asks only for governance events (sharing, permissions, seats, invites, tokens, plugins, SSO, SCIM, MFA, export and public link settings). Plain file views, creations, renames and moves are left out. IP addresses are never stored, and the free-text parts of an event are dropped. Only an allow-list of ids, permissions and settings is kept in details.
API token usage. The developer log shows each REST API and MCP request with the token name, token type and user. Configview stores counts per day, token, user and endpoint. IP address, city and country are never stored.
Rate limit. Figma limits requests per minute by endpoint tier, the seat type and the plan, tracked separately per token. Configview paces itself at 20 requests a minute for folders and webhooks and 10 a minute for metadata, logs and usage, which is the figure for a low seat. It never calls the file content endpoints, which allow a View or Collab seat only 20 requests a month. When Figma answers 429 Configview waits for the time Figma asks, up to five minutes, and then stops with an error.
Large organizations. Walking folders takes two requests per folder, so a team with hundreds of folders can take most of the 30-minute collector limit; walk_complete is 0 on a team whose walk was cut short. File Sharing checks the 200 most recently modified files per run.
What isn’t collected
- File content, layers, text, images, thumbnails and preview links
- Comments, variables, dev resources and library contents (library analytics are not collected)
- The webhook passcode and description, and the path or query of a webhook address. Only the host is stored
- IP addresses, cities and countries from the activity log and developer log
- File names (except publicly linked files), billing and payment data