Permissions and security
What an AI app can and cannot do on your FigWP account, what each permission on the approval page means, and how tokens, sites and your designs are protected.
On this page
Connecting an AI app to FigWP is an OAuth sign-in like connecting it to a calendar: you approve once, on a FigWP page, and can revoke at any time. This page is the plain-language version of what you approve.
The permissions
| On the approval page | What it allows |
|---|---|
| Read account | Your plan, pages used and left, connected sites and whether a plugin is linked |
| Read Figma | The frame you have selected in the open plugin: its layers, a preview, a render |
| Write Figma | One thing only: making an auto-layout copy of a frame next to it. Your original is never changed |
| Write site | Creating drafts, changing drafts FigWP created, reading a page’s elements, writing global colours and fonts |
| Publish | Publishing a draft FigWP created |
An app asks for all five. What it does with them is driven by what you ask in the chat; the app is not allowed anything these do not cover.
What an app cannot do
- Read a Figma frame you have not selected, or any file the plugin is not open in.
- Edit, publish or delete a page FigWP did not create.
- Read your site’s users, posts, settings or anything beyond the FigWP routes.
- See your access token, your password or your billing details.
- Act when the plugin is closed: every Figma job runs in the open plugin, against the current selection.
How the connection works
- The app signs in with OAuth 2.1: a short-lived code exchanged for a one-hour access token and a 30-day refresh token. Tokens are stored only as hashes.
- Refresh tokens rotate on every use. A refresh token presented twice disconnects the app, which protects you if one was copied.
- Changing or resetting your password disconnects every app. Disconnecting an app on the dashboard revokes every token it holds.
The plugin and your token
The access token identifies the account. The plugin stores it in Figma’s own storage on your computer, sends it only to FigWP, and never shares it with the AI app. Regenerating the token on the dashboard refuses the old one everywhere at once.
Your site
A connected site and FigWP share a secret that is exchanged directly between the site and FigWP, never through a browser. Every request between them is signed with it, carries a timestamp and a single-use nonce, and runs as the WordPress user who connected the site, with that user’s capabilities checked on every action. FigWP only calls https sites on public addresses.
Your designs and images
A conversion, and the images FigWP stores for it, are kept for 7 days and then deleted. Images are copied into your site’s media library on import, so the page does not depend on FigWP afterwards. Preview links for a draft expire after ten minutes and work for nothing else.