Who can use this feature
Organization and Enterprise plans
Admins only
OAuth apps connect external tools to Figma so people can use Figma content in other workflows. As an organization admin, you can manage which apps can access your organization’s resources, review requests, and approve the permissions each app needs.
These controls cover MCP clients, such as Cursor and Claude Code, and other OAuth apps that connect to Figma.
Note: This article reviews how admins manage app requests. To learn how to request app approval as a member of an organization, see Request approval to connect an app to Figma.
Note: This feature is rolling out gradually starting November 17, 2026. If you don't see it in your account yet, it should appear in the next few days.
How app approval works
You can choose whether people can connect any app or only apps you approve. The list of approved apps is your organization’s allowlist.
When you approve an app, you also approve its requested scopes. Scopes define what the app can do, such as read file content or create comments.
Approval applies across your organization. Each person still needs to authorize the app to connect to their own Figma account.
Require approval for apps
To change your app policy:
- From the file browser, click Admin.
- Select Extensions in the sidebar.
- Select the Apps tab.
- Click Settings.
- Choose an option:
- Allow all apps (default): People can connect apps without admin approval.
- Only admin-approved apps: Apps must be on your organization’s allowlist to access organization resources.
- If you require approval, choose whether to keep Allow plan members to request apps selected.
- Click Save.
Note: Admins can also access this setting from Admin > Settings > Connections > Apps.
When requests are enabled, members can request approval when they try to connect an unapproved app.
Warning: Requiring approval affects existing connections as well as new ones. Apps that aren’t on the allowlist lose access to your organization’s resources, including through connections people have already authorized. Review the apps your organization needs before changing this setting.
If you switch back to Allow all apps (default), connections blocked by the approval policy can resume. People may need to reconnect if their authorization has expired.
Approve an app
You can approve an app before someone requests it or approve it in response to a member’s request.
Approve a suggested app
To approve a suggested app:
- From Admin, select Extensions.
- Select the Apps tab.
- Find the app in the Suggested section.
- Click Approve.
Once approved, the app appears in your organization’s list of approved apps.
Add an app by link or client ID
You can add an app using its Figma Community URL or client ID. A client ID identifies a specific OAuth app. For apps that aren’t listed in Community, get the client ID from the app’s developer or setup documentation.
- From Admin, select Extensions.
- Select the Apps tab.
- Click Add app.
- Paste the app’s Figma Community URL or enter its client ID.
- Click Add app.
Once approved, the app appears in your organization’s list of approved apps.
Review app requests
When members request an app, you can review its permissions and decide whether to approve it for your organization.
- From Admin, select Dashboard.
- Find the app request in All requests, or filter the list to show app requests.
- Select the request to open its details.
- Review the app, requested permissions, and any reasons members provided.
- Choose an action:
- Approve app: Add the app and its requested permissions to your organization’s allowlist.
- Decline: Leave the app unapproved. You can provide a reason for your decision.
Members receive a notification about the decision. After approval, they still need to finish authorizing the app to connect to their Figma account.
Requests are grouped when they’re for the same app, organization, and set of permissions. If an app’s requested permissions change, requests submitted after the change appear in a separate group. For example, requests for an app that only reads files are grouped separately from later requests that also include permission to write to files.
Declining a request doesn’t permanently block future requests. Members can request the app again.
Review requests for additional permissions
An approved app may later request more permissions. For example, an app that previously only read file content might add the ability to write to files.
Additional permissions require approval before new connections can use them.
You can review requests for additional permissions alongside all of your other app requests.
- Approve adds the requested permissions to the app’s approval.
- Decline keeps the app’s previously approved permissions. The additional permissions remain blocked.
Declining additional permissions doesn’t remove the app from your allowlist. To stop the app from accessing organization resources, revoke its approval.
Revoke an app’s approval
If your organization requires app approval, you can remove an app from the allowlist to stop it from accessing organization resources.
- From Admin, select Extensions.
- Select the Apps tab.
- Select the app you want to remove.
- Click Revoke approval.
- Click Revoke approval again to confirm.
Revoking approval affects everyone using the app to access your organization’s resources. Existing connections lose access when the app next tries to access those resources.
Revoking organization approval doesn’t delete people’s individual app authorizations. Your organization’s policy blocks access to its resources.