Auth Tokens
Figma auth tokens help Desire perform Figma operations on your behalf. This document outlines steps to add Figma auth tokens into Desire, how tokens are used and managing them.
Adding Auth Tokens
Desire lets you add Figma tokens using the Desire + Figma Chrome extension. Once you have installed it, you will be prompted to follow the 3-step wizard.
How are auth tokens used?
As stated previously, auth tokens allow Desire to operate on your behalf in the Figma world. Whenever a user performs an action that requires communication with Figma, this token is used. If you have a valid token, things go well. If you have a token with problems, Figma will reject our calls. So, it is vital for us to ensure that we have valid tokens.
So, why do we need multiple tokens?
There are a couple of reasons.
(a) Every token has a life span, and they expire once that time pass by. Desire automatically detects and marks tokens as expired. If there is a situation where no active tokens exist, Desire will no longer be able to communicate with Figma
(b) Figma imposes rate limits, and may restrict repeated calls from the same token. Having multiple tokens will distribute load across all the tokens, reducing the risk of rate limiting.
Managing Tokens
Super Admins can manage auth tokens from the Figma Auth Pool application on the Admin Landing Page. The page displays all the available tokens with their statuses. Users will be able to toggle the status of tokens between active/inactive, or delete tokens.
Last updated