Extended/No Expiration Personal access tokens

I’m also finding the removal of this option to be a show-stopper. Please please bring it back!

​@ksn post IPO you stop caring about devs huh :( 

We basically can’t use any code connect or API features in any long lived pipeline unless we build our own agent to create new tokens at some cadence lol. I think you guys should monitor more for dropoff/usability, this is probably leading to a lot of companies being unable to use Figma’s APIs for a pretty dumb reason.

Hello, we should be able to at least have bot type accounts have a no-expiry token. By eliminating the no-expiry option, you now impose more work and convolution on maintenance of automation that takes place when using the Figma API. Please bring back the no-expiry option for bot-type accounts.

Hello, I’m also disappointed to see this feature go. We were about to launch a bunch of CI-optimized workflows for code connect, analytics, etc and the lack of a long-living token is a show stopper. Please consider bringing it back, at least for read-only permissions

Hello.

We are stuck to generate automatically tokens via CI too.

Please reconsider read-only long lived tokens !

This is absurd, it undermines all sorts of automated setups while providing no security gains whatsoever - in fact, it makes it worse by making us juggle tokens every couple of weeks. Please escalate this so that it becomes a priority.

So infuriating how apathetic large companies get. They really couldn’t think of extending it for read-only? Figma: I know you think you’re the most important tool in the world, but if someone got READ ONLY access to mocks it’s not going to take down that company 🤣

R&Ds are all focused on more "important" things, such as Figma Make. 🤣